(e.g., with the use of CPEs of different lengths or AGC symbol
puncturing).Please refer to RP-220300 for detailed scope of the WI.
R1-2205573 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
R1-2203981 Work plan for NR sidelink evolution OPPO
RAN1 study phase focusing on FR1 unlicensed bands (n46 and n96/n102) to be completed by RAN1#111.
R1-2204093 Discussion on V2X use cases, scenarios, and requirements for SL-U TOYOTA Info Technology Center
R1-2205113 Contention-Based Sidelink Burst Transmissions Johns Hopkins University APL
R1-2205118 General considerations on SL-U Continental Automotive GmbH
Including evaluation methodology for unlicensed channel access (if any).
R1-2205033 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
· Proposal 1: Study methods to introduce more transmission starting points in SL-U other than full-slot transmission to improve channel access probability.
· Proposal 2: Study how to introduce back-to-back transmissions over multiple consecutive slots in SL-U.
·
Proposal 3: Study starting
transmissions in one of a set of contention slots with granularity (e.g., with the use of CPEs of different lengths or AGC symbol
puncturing).
· Proposal 4: Study enhancements to the exclusion step in resource selection to limit the system throughput losses due to the issue of unused reserved resources due to LBT failures.
· Proposal 5: Study enhancements to resource reservation to reserve multiple consecutive slots as a way to silence other SL-U UEs and benefit in terms of LBT success probability and interference over the COT.
· Proposal 6: Study enhancements to resource reservation to signal the TDRA and FDRA within a COT and facilitate TDM and FDM COT sharing to other SL-U UEs.
· Proposal 7: Conditions can be considered and can be studied to determine when a UE is a valid receiver of a COT initiator UE. The study can include (without being restricted to) the following definitive conditions: 1) decoded SCI, 2) is within a range from the initiator
· Proposal 8: Introduce UE-to-UE COT sharing in SL-U with R16 NR-U as baseline, for at least the following behaviors:
o PSFCH to COT initiator
o PSFCH to UE other than COT initiator
o PSCCH/PSSCH to a group of UEs including the COT initiator
· Proposal 9: Study how to introduce COT-SI indication in SL-U, to provide indication of the bandwidth and duration of an ongoing COT.
·
Proposal 10: Study methods to enable for initiating UE to resume
transmissions in its COT after a gap longer than 25 
· Proposal 11: Reuse evaluation methodology from Rel-16 NR-U study as much as possible with possible adjustments.
· Proposal 12: Studies can focus on Pc5 links over the unlicensed spectrum BW.
· Proposal 13: Study layouts with two operators, where a first SL-U system is evaluated in the presence of one of an NR-U system, a WiFi system, or a second SL-U system.
· Proposal 14: Reuse layouts for indoor and outdoor from the Rel-16 NR-U study, where NR-U and WiFi operators are deployed as in [4], and the SL-U operator (or operators) are deployed uniformly at random in the area.
· Proposal 15: Support the following SL-U topology in system evaluation
o Pair-wise SL-U topology (baseline), where pairs for SL-U UEs are dropped uniformly in the region of interest
o Star topology (optional), where the central SL-U UE is associated with multiple peripheral SL-U UEs
Decision: The document is noted.
R1-2204802 On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
· Proposal 1: SL operating is unlicensed spectrum supports both dynamic and semi-static channel access mode.
· Proposal 2: The channel access types defined in Rel.16 NR-U (i.e., type 1, type 2A, 2B and 2C) are supported in SL operating in unlicensed spectrum. FFS: when to use them based on the type of SL channels and signals transmitted and based on COT sharing conditions.
· Proposal 3: RAN1 should agree on the exact interpretations of the intended deployment for mode-1:
o Mode-1-a: a gNB sends scheduling DCI on the licensed carrier, and can perform sensing on SL unlicensed carrier, but it is not allowed to transmit on the SL unlicensed carrier.
o Mode-1-b: a gNB sends scheduling DCI on the licensed carrier and cannot either perform sensing or transmit on SL unlicensed carrier.
· Proposal 4: RAN1 should study a unified procedure for both mode 1 and mode 2 to allow a UE to share its COT with other UE(s).
· Proposal 5: When operating an NR-U SL system in dynamic channel access mode, the contention windows size adjustment for channel access type 1 needs to be enhanced.
· Proposal 6: RAN1 should discuss how to relate the ProSe Per Packet Priorities (PPPP) defined in SL and the Channel access priority classes (CAPC), since the latest must be supported for compliance to regulatory requirements. Furthermore, RAN1 should send an LS to RAN2 for the identified issue.
· Proposal 7: RAN1 should discuss whether to support sub-channelization and in case should study mechanisms to mitigate mutual blocking across frequency multiplexed transmissions.
· Proposal 8: RAN1 should investigate mechanisms to mitigate interference across UEs transmitting in a TDMed manner, since different UEs could have overlapping pool of resources and can potentially start transmission at the same time.
· Proposal 9: RAN1 should investigate the impact of the ON/OFF and OFF/ON transient period to the LBT procedure performed by a UE when transmission of a PFSCH may require LBT and a SL slot may contain a PSFCH transmission.
· Proposal 10: RAN1 should discuss how to combine the LBT procedure with the SL sensing and resource selection procedure.
· Proposal 11: At least both S-SSB and PSFCH could be qualifies as a short control signalling. In this sense RAN1 should further discuss and converge on how to interpret the ETSI BRAN related text:
o Option 1: As long as these signals meet the minimum requirements to qualify as a short control signalling, they can be transmitted without LBT.
o Option 2: As long as these signals meet the minimum requirements to qualify as a short control signalling, a UE may transmit them using type 2A LBT.
Decision: The document is noted.
R1-2203713 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
· Proposal 1: Support Type 1, Type 2A, Type 2B, and Type 2C channel access procedure for SL transmission on unlicensed spectrum
o For Type 1 SL channel access procedure, Type 1 DL channel access procedure is a baseline
§ FFS: How to update contention window size adjustment for PSCCH/PSSCH with and without SL HARQ-ACK feedback enabled or with groupcast SL HARQ-ACK feedback Option(s)
§ FFS: Granularity of maintaining contention window size (e.g., cast type, unicast session, SL HARQ-ACK feedback option, SL channel type)
o For Type 2A/2B/2C SL channel access procedure, Type 2A/2B/2C DL channel access procedure are reused, respectively
o FFS: Applicable scenario of each channel sensing type (e.g., physical channel type, within/outside COT duration)
· Proposal 2: For SL transmission, energy detection threshold adaptation procedure for UL is considered as a baseline
o FFS: Energy detection threshold for S-SSB transmission
· Proposal 3: For SL Mode 1 operation on unlicensed spectrum, it is necessary to decide whether or how to introduce Mode 1 reporting for consecutive LBT failure
· Proposal 4: Support COT (channel occupancy time) duration shared by a UE for SL transmission.
o FFS: Granularity of SL transmission(s) that can share the same COT duration.
· Proposal 5: For COT duration shared by a UE for SL transmission, one or more of followings are supported:
o Option 1: COT duration initiated by gNB including DL transmission
§ Option 1-1: Group-common DCI (e.g., DCI format 2_0) indicates the remaining COT duration
· FFS: Whether or how to differentiate link type applying the indicated COT duration
§ Option 1-2: DCI format 3_0 indicates channel access type and CP extension type to be applied to at least first SL transmission
§ FFS: DCI formats for DL assignment or UL grant (e.g., DCI format 0_0/0_1/0_2/1_0/1_1/1_2)
o Option 2: COT duration initiated by a UE including SL transmission
§ Option 2-1: SCI can indicate channel access type to be applied to the corresponding PSFCH transmission
§ Option 2-2: At least for unicast, TX UE can indicate COT duration that can be used by RX UE for its PSCCH/PSSCH transmission to the TX UE
o Option 3: COT duration initiated by a UE including UL transmission
§ FFS: Whether or how a UE indicating COT duration can use a subset of the COT duration for its SL transmission
· Proposal 6: For semi-static COT sharing, it is necessary to investigate how to set FFP (fixed frame period) and what is the granularity of configuration for FFP
· Proposal 7: For processing order of SL resource (re)selection procedure, followings are supported:
o Option A: UE performs SL resource (re)selection procedure and then performs channel access procedure for the selected resources
o Option B: UE performs channel access procedure first then performs SL resource (re)selection procedure
o FFS: Applicable scenario of Option A and/or Option B
· Proposal 8: For SL resource (re)selection procedure, one or more of followings are considered:
o Whether or how to ensure processing time for channel access procedure between SL resources.
o Whether or how to support SL burst transmission to reduce channel sensing overhead.
o Whether or how UE further excludes resources associated with channel sensing interval of other UE’s reserved resources.
o Whether or how to consider channel sensing results associated with other UE’s reserved resources.
o Whether or how to consider COT duration
§ Whether or how to consider COT duration that is available for SL transmission
§ Whether or how to exclude resources within COT duration that is not available for SL transmission
· Proposal 9: For evaluating coexistence between WiFi and SL communication on unlicensed spectrum,
o For reference system, followings are considered:
§ Sub7GHz outdoor scenario as specified in TR 38.889
§ Table A.1.2-1 in TR 38.889.
§ Both operators deploy WiFi APs.
o For NR SL on unlicensed spectrum, followings are considered:
§ Sub7GHz outdoor scenario as specified in TR 38.889 with following modification
§ For pathloss/fast fading/traffic model for P2P link as specified in R1-2105203 is reused.
§ One operator deploys WiFi APs while another operation deployment is replaced with UE deployment
· Proposal 10: For evaluation purpose of SL on unlicensed spectrum, SL communication for commercial use cases are prioritized.
Decision: The document is noted.
R1-2203122 On Channel Access Mechanism and Evaluation Methodology for SL-U Nokia, Nokia Shanghai Bell
R1-2203146 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2203331 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2203365 Discussion on channel access mechanism for SL-U ZTE, Sanechips
R1-2203461 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2203561 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2203645 SL Channel access in unlicensed spectrum InterDigital, Inc.
R1-2203657 Discussion on channel access mechanism for sidelink on unlicensed spectrum China Telecom
R1-2203693 Channel Access of Sidelink on Unlicensed Spetrum NEC
R1-2203703 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2203734 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2203749 Sidelink channel access on unlicensed spectrum Panasonic Holdings Corporation
R1-2203818 Channel access mechanism for sidelink-unlicensed xiaomi
R1-2203906 On channel access mechanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2203982 Access mechanisms of NR sidelink in unlicensed channel OPPO
R1-2204084 SL-U General Access Considerations CableLabs, Charter Communications
R1-2204097 Discussion of channel access mechanism for sidelink transmission in unlicensed spectrum FUTUREWEI
R1-2204194 Discussion on sidelink on unlicensed spectrum ASUSTeK
R1-2204247 On channel access mechanism for sidelink on FR1 unlicensed spectrum Apple
R1-2204306 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2204382 Discussions on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2204427 Discussions on Channel access mechanism for NR sidelink evolution Sharp
R1-2204552 Discussion on channel access mechanism for SL on unlicensed spectrum WILUS Inc.
R1-2204580 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2204607 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2204730 Discussion on Channel access mechanism MediaTek Inc.
R1-2204741 Channel access mechanism for SL-U Ericsson
R1-2204868 Discussion on channel access mechanism for sidelink on unlicensed spectrum ROBERT BOSCH GmbH
R1-2205082 Considerations on unlicensed channel access for SL-U Fujitsu Limited
[109-e-R18-SL-01] – Kevin (OPPO)
Email discussion on channel access mechanism by May 20
- Check points: May 16, May 20
R1-2205180 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2205181 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
(May 16th GTW session)
R1-2205182 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From May 19th GTW session
Agreement
Type 1 and Type 2 (2A/2B/2C) channel access procedures, transmission gap and LBT sensing idle time requirements specified in TS37.213 for NR-U are taken as baseline for NR sidelink operation in a shared channel.
· FFS conditions for the actual channel access type(s) used for each SL channel and signal transmitted, and based on COT sharing conditions (if supported)
· FFS whether UL CAPC or DL CAPC or both should be used as the baseline,
o FFS how the channel access priority classes apply to each SL channel and signal
o FFS sidelink priority levels (PQI or L1 priority), channel and signal mapping to the 4 channel access priority classes. The discussion may involve other WGs.
Agreement
· UE-to-UE COT sharing is supported in NR sidelink operation in a shared channel (SL-U).
o FFS applicable SL channels and signals (e.g., PSCCH/PSSCH, PSFCH, S-SSB) for shared COT access and any restrictions (e.g. whether the COT can be shared with a single UE or multiple UEs)
o FFS all other details in compliance with the regulatory requirements
· CP extension (CPE) is supported for NR sidelink operation in a shared channel.
o FFS all remaining details including applicable scenarios, usage, PHY structure, etc.
Agreement
Channel access procedures for transmission(s) on multiple channels are supported for NR sidelink operation as defined by TS37.213 for NR-U (wherever applicable)
· FFS whether the downlink, uplink and/or semi-static multiple channel access procedure(s) (if supported) from NR-U should be used as a baseline and whether/how they are applied in SL mode 1 and mode 2 operation
R1-2205183 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From May 20th GTW session
Agreement
·
The existing sidelink mode
1 RA including dynamic grant, Type 1 and Type 2 configured grants are supported
as a baseline for sidelink operation in a shared carrier, subject to applicable
regional regulations. At least in dynamic channel access, SL UE performs Type 1
or one of the Type 2 LBTs before SL transmission using the allocated
resource(s), in compliance with transmission gap and LBT sensing idle time
requirements specified in TS37.213.
o FFS whether/how mode 1 resource allocation selection
procedure needs to be updated / enhanced due to shared spectrum channel
access
· The existing sidelink mode 2 RA schemes are supported as a baseline for sidelink operation in a shared carrier, subject to applicable regional regulations. At least in dynamic channel access, SL UE performs Type 1 or one of the Type 2 LBTs before SL transmission using the selected and/or reserved resources, in compliance with transmission gap and LBT sensing idle time requirements specified in TS37.213.
o FFS whether/how mode 2 resource selection procedure needs to be updated / enhanced due to shared spectrum channel access
· FFS whether/how multi-consecutive slots transmission can be supported for NR sidelink operation in unlicensed spectrum, including the following aspects
o channel access, resource allocation and PHY channel design
· FFS whether/how enhancement is needed between the end of the LBT procedure and the start of the SL transmission to retain channel access
· RAN1 to strive for a common solution for channel access for Mode 1 and Mode 2
Final summary inR1-2205184.
R1-2203907 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
Proposal 1: The study shall include investigating the following sidelink signals and channels to operate on unlicensed spectrum, subject to the regulation requirements:
· PSSCH
· PSCCH
· PSFCH
· S-SS/PSBCH block
· sidelink reference signals
Proposal 2: To satisfy OCB and PSD requirements, it’s beneficial to support interlace based sub-channel and resource pool for sidelink on unlicensed spectrum.
· The structure of the interlace can use Rel-16 NR-U as a baseline.
· Further study whether enhancement for the structure of the interlace is needed (e.g. sub-RB interlace).
· Further study the resource allocation of PSSCH, PSCCH, PSFCH, and sidelink RS in the interlace based resource pool, and associated indication method and transmission/reception procedures.
Proposal 3: To satisfy OCB and PSD requirements, it’s beneficial to support frequency domain enhancement to S-SS/PSBCH block, and study at least the following approaches:
· Multiplexing of S-SS/PSBCH block with other sidelink signal/channel;
· New S-SS/PSBCH block structure with a wider bandwidth;
· S-SS/PSBCH block repetition in the frequency domain;
· Interlace based S-SS/PSBCH block structure.
Proposal 4: It’s beneficial to support mechanisms to reduce the number of channel access procedures for SL-U, and RAN1 shall investigate at least the following in the study:
· Mechanism to eliminate or shorten the time domain gap in sidelink transmissions, e.g. symbol repetition and CP extension.
· Mechanism to support multi-slot based PSSCH/PSCCH transmission.
Proposal 5: It’s beneficial to support mechanisms to allow immediate transmission after successful channel access procedure for SL-U, and RAN1 shall investigate at least the following in the study:
· Mechanism to support multiple starting locations for PSSCH/PSCCH transmission in a slot.
· Mechanism to support sidelink wake-up-signal that can be transmitted immediately after successful channel access procedure.
Proposal 6: It’s beneficial to support mechanisms to compensate transmission dropping due to failed channel access procedure for SL-U, and RAN1 shall investigate at least the following in the study:
· Mechanism to support flexible association for PSFCH transmission occasions, and allow extra transmission occasion for a HARQ-ACK feedback if channel access procedure fails.
· Mechanism to support S-SS/PSBCH block transmission window with extra transmission occasions to mitigate the impact of channel access procedure failures.
Decision: The document is noted.
R1-2203147 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
Proposal 1: Definition of SL-BWP and resource pool are reused for SL-U.
Proposal 2: A resource pool is configured to include one or multiple 20MHz LBT channels.
Proposal 3: Further study how to avoid slot-level transmission gaps in a resource pool to maintain a COT, e.g., whether bitmap of resource pool should be set to all “1”s.
Proposal 4: Study to introduce two sidelink starting symbol locations in a lot, where possible starting symbol locations can be reused from Rel-16 NR-V to reduce unnecessary specification workload.
Proposal 5: Reuse CP extension as defined in Rel-16 NR-U for SL-U for symbol boundary alignment as well as reducing gap duration within a COT.
Proposal 6: Both contiguous RB in R16 NR-V and interlaced RB in R16 NR-U are supported for SL-U.
· The resource allocation granularity is one sub-channel as in R16 NR-V
· For interlace-based transmission, one subchannel equals to one interlace
Proposal 7: For PSCCH and PSSCH, both contiguous RB-based and interlaced RB-based transmission are supported. For both types of transmissions,
· PSCCH is always transmitted within one subchannel
· R16 NR-V PSCCH and PSSCH multiplexing is reused, i.e., PSCCH locates in the lowest subchannel of the subchannel(s) of corresponding PSSCH
Proposal 8: For PSFCH format in SL-U
· At least Rel-16 PSFCH format 0 is supported
· Further study whether to additionally introduce a new PSFCH format, including whether the new format can be multiplexed with PSSCH.
Proposal 9: For PSFCH transmission, further study how to meet OCB requirement, e.g., interlaced transmission, or common PSFCH interlace, etc.
Proposal 10: Further study the locations of PSFCH resources within a COT, e.g., (pre-)configured periodic locations, or dynamically indicated locations, etc.
Proposal 11: For PSSCH and PSFCH mapping in SL-U,
· When PSSCH and its related PSFCH are within the same COT, R16 NR-V implicit mapping is reused
· Otherwise, further study on PSSCH-PSFCH mapping, e.g., explicitly or implicitly.
Proposal 12: Further study the locations of S-SSB resources, e.g., whether/how to transmit additional S-SSB in addition to (pre-)configured periodic S-SSB occasions in case of LBT failure.
Proposal 13: For S-SSB transmission, further study how to meet OCB requirement, e.g., interlaced transmission, or multiplexing with other SL channels within a COT, etc.
Decision: The document is noted.
R1-2203123 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2203332 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2203366 Discussion on physical layer structures and procedures for SL-U ZTE, Sanechips
R1-2203462 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2203562 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2203646 SL U physical layer design framework InterDigital, Inc.
R1-2203694 Discussion on physical channel design framework NEC
R1-2203704 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2203714 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2203735 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2203750 Physical channel design for sidelink on unlicensed spectrum Panasonic Holdings Corporation
R1-2203819 Physical channel design for sidelink-unlicensed xiaomi
R1-2203983 Physical channel designs of NR sidelink in unlicensed channel OPPO
R1-2204085 Discussion on resources on sidelink operation in unlicensed spectrum CableLabs
R1-2204098 Discussion of physical channel designs for sidelink transmission in unlicensed spectrum FUTUREWEI
R1-2204121 Discussion on Physical channel design framework for sidelink on unlicensed spectrum Hyundai Motors
R1-2204248 On physical channel design framework for sidelink on FR1 unlicensed spectrum Apple
R1-2204307 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2204383 Discussions on channel design framework in SL-U NTT DOCOMO, INC.
R1-2204428 Discussions on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2204553 Discussion on PHY channel design framework for SL on unlicensed spectrum WILUS Inc.
R1-2204581 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2204608 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2204731 Discussion on Physical channel design framework MediaTek Inc.
R1-2204742 PHY channel design framework for SL-U Ericsson
R1-2204803 On the Enhancements to the Physical Channel Design for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2205034 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
[109-e-R18-SL-02] – Mixiang (Huawei)
Email discussion on physical channel design framework by May 20
- Check points: May 16, May 20
R1-2205238 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
R1-2205239 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
R1-2205240 FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From May 20th GTW session
Agreement
SL BWP, SL resource pool in R16/R17 NR SL and RB set in R16 NR-U are reused for SL-U as baseline
· Only one SL BWP is (pre-)configured within a carrier
· The SL BWP is (pre-)configured to include one or multiple SL resource pools
· At least support that one SL resource pool can be (pre-)configured to include integer number of RB sets
o FFS: whether/how to support one SL resource pool can include sub-set of PRBs of one RB set
o FFS: the applicable resource pool
o FFS: the impact on sub-channel size and number of sub-channels in a resource pool if sub-channel is supported
· PRBs within intra-cell guard band of two adjacent RB sets belong to a resource pool if the resource pool includes the two adjacent RB sets
o FFS details, e.g., how such PRBs are used, the applicable resource pool, etc.
· FFS: whether R16/R17 NR SL S-SSB slots and/or new S-SSB slots (if supported) are excluded from resource pool
· FFS: which slots belong to resource pool, e.g., how to set the value of bitmap, whether to consider SL-U/NR-U operating in the same carrier and whether TDD configuration are considered, etc.
· FFS: the impact of PSCCH/PSSCH mapping to frequency resources on resource pool configuration, on sub-channel definition if sub-channel is supported, etc.
Agreement
For PSCCH and PSSCH in SL-U:
· Both R16/R17 NR SL contiguous RB-based and R16 NR-U interlace RB-based transmissions are considered as starting point
o RAN1 strives to have unified design for both contiguous RB-based and interlace RB-based transmissions
o FFS: whether/how to address IBE (In Band Emission) impact
Agreement
For PSCCH and PSSCH in SL-U:
· For interlace RB-based transmission (if supported), at least the following candidates can be discussed:
o Frequency domain resource allocation granularity is one sub-channel for PSSCH transmission
§ FFS: Other resource allocation granularity, e.g., RB-level
o 1 sub-channel equals K interlaces if sub-channel is supported
§ FFS details
o Other candidates are not precluded
o FFS: mapping of PSCCH to frequency resources
o FFS: resource indication in time/frequency domain, e.g., how to handle using one RB set or multiple RB sets, etc.
Agreement
For slot structure in SL-U:
· At least R16/R17 NR SL slot-based PSCCH/PSSCH transmission is supported
o FFS: whether/how to support additional starting symbol(s) within a slot for the PSCCH/PSSCH transmission
Agreement
For PSFCH and SL-HARQ in SL-U:
· At least R16 NR SL PSFCH format 0 is supported
o FFS whether to introduce new PSFCH format
· FFS: how to meet OCB and PSD requirement for PSFCH transmission, e.g., using interlaced RB transmission, whether/how to avoid too small PSFCH capacity, etc.
· FFS: the locations of PSFCH resources, e.g., (pre-)configured, dynamically indicated, etc.
· FFS: whether/how to address PSFCH transmission dropping due to LBT failure, e.g., whether to have multiple PSFCH occasions for a PSSCH and the related PSSCH-PSFCH mapping relationship, impact on SL HARQ-ACK reporting to the gNB for Mode 1, etc.
· FFS: whether/how to address PSFCH and related PSSCH in different COTs
Agreement
For S-SSB and synchronization in SL-U:
· FFS the time domain locations of S-SSB resources, e.g., whether/how to introduce more candidate occasions compared with R16/R17 NR SL design, etc.
· Down-selection at least one of the following solutions to meet OCB and PSD requirement for S-SSB transmission
o Option 1: Using interlaced RB transmission
o Option 2: S-SSB multiplexing with other SL transmissions in the same slot
o Option 3: Repetition of S-PSS/S-SSS/PSBCH in frequency domain
o Option 4: S-PSS/S-SSS/PSBCH with wider bandwidth
· FFS: whether to support 4 symbols S-SSB
o Note: 4 symbols S-SSB can be considered with options 1/2/3/4 above
· FFS whether the temporary exemption of OCB requirement is applicable for S-SSB transmission
· FFS whether any changes to R16/R17 NR SL synchronization procedure
Final summary in R1-2205241.
R1-2204867 On co-channel coexistence between LTE and NR sidelink ROBERT BOSCH GmbH
Proposal 1: LTE-NR coexistence schemes needs to guarantee:
· no changes on the lower layers of existing LTE V2X devices
· a solution that can be easily retrofitted to R16/R17 (if needed)
· avoiding adoption of LTE protocol stack in NR devices as much as possible
Proposal 2: Study resource pool separation between LTE and NR sidelink using static FDM and TDM (pre-)configuration
Proposal 3: Study possible quasi-dynamic co-channel coexistence between LTE and NR V2X based on detect-and-vacate of shared resources.
Proposal 4: Study if extending quasi-dynamic/detect-and-vacate coexistence mechanism may support coexistence with non-3GPP technologies.
Proposal 5: For dynamic spectrum sharing between LTE and NR V2X study whether:
· Discovery/sensing of LTE sidelink transmission (by NR V2X devices) is possible or energy detection only is sufficient
· NR V2X Rel-16 pre-emption and/or re-evaluation can be enhanced to avoid collision with concurrent LTE V2X transmissions.
Decision: The document is noted.
R1-2204720 On co-channel coexistence between LTE sidelink and NR sidelink MediaTek Inc.
Proposal 1: Study for SL co-channel coexistence solutions should take into account the following aspects.
· Prioritize performance evaluations of existing Rel-16 design to assess the need for any enhanced solutions.
· Evaluations should be performed based on a common set of simulation scenarios and parameters.
· Narrow down which specific scenarios (e.g., NR Mode-2 coexisting with LTE Mode-4), if any, require enhancement for coexistence support.
Proposal 2: Semi-static resource pool separation approach in time-domain (based on Rel-16 NR V2X long-term TDM) is supported in Rel-18 for co-channel coexistence as a baseline solution.
Proposal 3: Further coexistence solutions (including dynamic based mechanisms) can be studied and evaluated for their potential benefits vs. complexities.
Proposal 4: Use the simulation parameters provided in Table I and follow TR 37.885 evaluation methodology as guideline to evaluate potential coexistence solutions.
Decision: The document is noted.
R1-2203984 Discussion on co-channel coexistence for LTE and NR V2X OPPO
· Proposal 1: Both semi-static partitioning of resources and dynamic sharing of resources between LTE V2X and NR V2X should be considered.
· Proposal 2: NR module performs resource exclusion based on the SL grant determined by LTE module to address the in-device coexistence issue in the same frequency channel.
Decision: The document is noted.
R1-2203124 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
· Proposal 1: RAN1 to study mechanisms that enable dynamic co-channel coexistence.
· Proposal 2: RAN1 to study mechanisms that enable dynamic co-channel coexistence in full co-channel overlap.
· Observation 6: In a co-channel coexistence setting a NR SL transmission may degrade an LTE SL transmission/reception.
· Proposal 3: RAN1 to study conditions where a NR SL transmission should be dropped (i.e. apply Rel-16 In-device coexistence framework) to protect an LTE SL transmission/reception.
· Proposal 4: RAN1 to study mechanisms (beyond applying the Rel-16 In-device coexistence framework). E.g. allow a NR SL device to avoid resources that are expected to impact an LTE SL transmissions/reception.
· Proposal 5: RAN1 to study the NR SL device capabilities assumptions when coexisting with LTE SL.
· Proposal 6: RAN1 to clarify if NR SL only devices or devices which cannot exchange information between the LTE module and the NR module in a timely manner are allowed to use LTE SL spectrum.
· Proposal 7: Any co-channel coexistence mode requires slot and subframe boundary alignment between LTE and NR SL.
· Proposal 8: TDM based co-channel coexistence requires DFN/SFN alignment between LTE and NR SL.
· Proposal 9: RAN1 should discuss whether NR SL synchronization based on LTE SLSS/PSBCH transmissions and/or LTE SL synchronization based on NR transmissions are supported and if synchronization procedures need to be updated.
Decision: The document is noted.
R1-2203148 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2203333 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2203367 Study on co-channel coexistence for LTE sidelink and NR sidelink ZTE, Sanechips
R1-2203463 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2203563 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2203642 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
R1-2203658 Discussion on co-channel coexistence for LTE sidelink and NR sidelink China Telecom
R1-2203668 Discussion on Sidelink Co-channel Coexistence Panasonic Holdings Corporation
R1-2203695 Co-existence between LTE and NR sidelink NEC
R1-2203705 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2203715 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2203736 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sony
R1-2203820 Discussion on co-channel coexistence for LTE and NR sidelink xiaomi
R1-2203908 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2204049 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2204249 On co-channel coexistence for LTE sidelink and NR sidelink Apple
R1-2204308 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2204384 Discussions on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2204429 Discussions on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2204585 Considerations on co-channel coexistence for LTE SL and NR SL CAICT
R1-2204609 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2204652 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2204740 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2205035 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated
R1-2205119 General considerations on Coexistence between LTE- and NR-sidelink Continental Automotive GmbH
[109-e-R18-SL-03] – Sarun (Fraunhofer)
Co-channel coexistence for LTE SL and NR SL by May 20
- Check points: May 16, May 20
R1-2205204 FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From May 12th GTW session
Agreement
For co-channel coexistence in Rel-18, no changes in the LTE SL specifications are allowed.
Agreement
For co-channel coexistence in Rel-18, Rel-16/17 simulation assumptions are reused for evaluation of solutions, except for the UE dropping model.
· FFS: UE dropping model
R1-2205205 FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
R1-2205206 FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
Decision: As per email decision posted on May 21st,
Agreement
For the study of co-channel coexistence solutions in Rel-18, the combination of operational modes Mode 2 NR SL with Mode 4 LTE SL (Combination A) is considered with high priority.
· FFS: Whether/how to support Mode 1 NR SL + Mode 4 LTE SL (Combination B) and/or Mode 2 NR SL + Mode 3 LTE SL (Combination C).
Agreement
For evaluation of co-channel coexistence solutions in Rel-18, support the inclusion of dual module devices with NR+LTE modules using the following UE dropping models:
· UE Dropping Model A: The distance between 1 LTE SL module and 1 NR SL module are maintained as zero to model a co-located dual module device. The inter-device distance between any two adjacent devices in the same lane, which may be either a single module or a dual module device, is modified by doubling the time in the upper limit, resulting in max{2 meter, an exponential random variable with the average of the speed * 4sec}.
· UE Dropping Model B: The distance between 1 LTE SL module and 1 NR SL module are maintained as zero to model a co-located dual module device. The inter-device distance between any two adjacent devices in the same lane, which may be either a single module or a dual module device, is maintained the same as current assumptions, i.e., max{2 meter, an exponential random variable with the average of the speed * 2sec}.
Companies should mention the UE dropping model and the distribution of each device type (single/dual module) used in their simulation assumptions.
Agreement
Feasibility of semi-static resource pool partitioning and dynamic resource sharing as possible solutions for co-channel coexistence are to be studied.
Agreement
For studying the feasibility of dynamic resource sharing as a possible solution for co-channel coexistence,
· For device type A, the NR SL module uses the sensing and resource reservation information shared by the LTE SL module.
o FFS details on how the NR SL module uses this information.
o FFS details on how the LTE SL module shares the information to the NR SL module, exact information shared, timeline etc.
· FFS: Whether/how to define other method(s) for device type A to be aware of resources being occupied by LTE SL.
· FFS: Whether/how device type B should be supported.
Final summary in R1-2205588.
Placeholder only. This part of the work is to start after RAN1#110 pending RAN decision. No contributions in RAN1#109-e.
Placeholder only. This part of the work is to start after RAN1#110 pending RAN decision. No contributions in RAN1#109-e.
R1-2203368 Analysis on channel access efficiency of SL-U ZTE, Sanechips
R1-2203464 Discussion on the scopes of Rel-18 Sidelink evolution CATT, GOHIGH
R1-2203647 SL U QoS management InterDigital, Inc.
R1-2203667 Discussion on sidelink operation on unlicensed spectrum vivo
R1-2203985 Coexistence evaluation of SL-U and Wi-Fi OPPO
R1-2204250 On other topics of NR sidelink evolutions Apple
R1-2204743 Other aspects related to SL-U Ericsson
R1-2204912 Further consideration on evaluation methodology for sidelink operation over unlicensed spectrum Huawei, HiSilicon
Please refer to RP-221798 for detailed scope of the WI.
R1-2208146 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
[110-R18-SL] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Kevin (OPPO)
RAN1 study phase focusing on FR1 unlicensed bands (n46 and n96/n102) to be completed by RAN1#111.
Including evaluation methodology for unlicensed channel access (if any).
R1-2205744 Channel access mechanism for sidelink operation in unlicensed spectrum FUTUREWEI
R1-2205839 On Channel Access Mechanism and Evaluation Methodology for SL-U Nokia, Nokia Shanghai Bell
R1-2205850 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
R1-2205886 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2205991 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2206041 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2206119 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2206171 Discussion on channel access mechanism for SL-U Fujitsu
R1-2206290 Access mechanisms and resource allocation for NR sidelink in unlicensed channel OPPO
R1-2206400 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2206438 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2206448 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2206469 Channel Access of Sidelink on Unlicensed Spetrum NEC
R1-2206585 Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2206644 Discussion on channel access mechanism for sidelink-unlicensed Xiaomi
R1-2206669 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2206691 Discussion on channel access mechanism for sidelink on unlicensed spectrum China Telecom
R1-2206826 On channel access mechanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2206860 On Channel Access Mechanism for SL-U ITL
R1-2206913 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2207015 Discussion on channel access mechanism MediaTek Inc.
R1-2207110 Discussion of Channel Access Mechanisms Johns Hopkins University APL
R1-2207128 SL Channel access in unlicensed spectrum InterDigital, Inc.
R1-2207233 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2207279 Discussion on Channel access mechanism for NR sidelink evolution Sharp
R1-2207298 Sidelink channel access on unlicensed spectrum Panasonic
R1-2207337 Channel access mechanism for sidelink on FR1 unlicensed band Apple
R1-2207408 Discussion on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2207504 Discussion on sidelink on unlicensed spectrum ASUSTeK
R1-2207511 Discussions on channel access mechanism for sidelink on unlicensed spectrum ROBERT BOSCH GmbH
R1-2207566 Channel access mechanism for SL-U Ericsson
R1-2207599 Discussion on channel access mechanism for SL on unlicensed spectrum WILUS Inc.
R1-2207709 Discussion on channel access mechanism for SL-U ZTE,Sanechips (rev of R1-2206097)
R1-2207743 On Evaluation Methodology for SL-U CableLabs, Broadcom, Charter Communications (rev of R1-2207136)
R1-2207789 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Monday session
Agreement
The following evaluation scenario can be used for evaluating performance of SL-U designs, resource allocation schemes, and coexistence study with another RAT in a shared channel.
R1-2207790 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Wed session
Agreement
Agreement
R1-2207791 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2207792 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
Agreement
Multi-consecutive slots transmission (MCSt) is supported for Mode 1 and Mode 2 resource allocation in SL-U.
· FFS details
Agreement
· For UE-to-UE COT sharing, continue considering the following alternatives:
o Alt. 1: A responding SL UE can utilize a COT shared by a COT initiating UE when the responding SL UE is a target receiver of the at least COT initiating UE’s PSSCH data transmission in the COT.
§ When the responding UE uses the shared COT for its transmission has an equal or smaller CAPC value than the CAPC value indicated in a shared COT information
§ FFS any additional conditions
o Alt. 2: A responding SL UE can utilize a COT shared by a COT initiating UE when the responding SL UE is a target receiver of the COT initiating UE’s transmission in the COT.
§ When the responding UE uses the shared COT for its transmission has an equal or smaller CAPC value than the CAPC value indicated in a shared COT information
§ FFS how to determine a SL UE is a target receiverFFS: details of the channel type of the COT initiating UE’s transmission
§ FFS any additional conditions
o For Alt1 and Alt2: When a responding UE uses a shared COT for its transmission(s), the COT initiating UE is a target receiver of the responding UE’s transmission(s).
§ FFS: details of the channel type of the responding UE’s transmission(s)
· gNB relaying/forwarding a UE initiated COT to another UE is not supported in Rel-18
· FFS whether a Mode 1 UE can report a COT or related information to gNB for aiding Mode 1 RA
Final summary in R1-2207793.
R1-2205745 Physical channel design for sidelink operation in unlicensed spectrum FUTUREWEI
R1-2205840 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2205851 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2205887 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2205992 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2206042 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2206098 Discussion on physical layer structures and procedures for SL-U ZTE,Sanechips
R1-2206120 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2206291 Physical channel designs of NR sidelink in unlicensed channel OPPO
R1-2206401 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2206439 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2206449 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2206470 Discussion on physical channel design framework NEC
R1-2206586 Physical Channel Design for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2206645 Discussion on physical channel design for sidelink-unlicensed Xiaomi
R1-2206661 Discussion on Physical channel design framework for sidelink on unlicensed spectrum Hyundai Motor Company
R1-2206670 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2206827 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
R1-2206861 On Physical Channel Design framework for SL-U ITL
R1-2206914 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2207016 Discussion on physical channel design framework MediaTek Inc.
R1-2207064 Physical channel design for sidelink on unlicensed spectrum EURECOM
R1-2207111 Discussion on Design of Short Synchronization Signals Johns Hopkins University APL
R1-2207129 SL U physical layer design framework InterDigital, Inc.
R1-2207234 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2207280 Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2207299 Physical channel design for sidelink on unlicensed spectrum Panasonic
R1-2207338 Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum Apple
R1-2207409 Discussion on channel design framework in SL-U NTT DOCOMO, INC.
R1-2207567 PHY channel design framework for SL-U Ericsson
R1-2207600 Discussion on PHY channel design framework for SL on unlicensed spectrum WILUS Inc.
R1-2207795 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Monday session
Agreement
For PSCCH and PSSCH in SL-U:
· Both R16/R17 NR SL contiguous RB-based and interlace RB-based transmissions similar to R16 NR-U are supported
R1-2207796 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
R1-2207797 FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Wed session
Agreement
For PSCCH and PSSCH in SL-U:
Agreement
To meet OCB and PSD requirement for PSFCH transmission, at least RB-based interlace is supported at least for 15 kHz and 30 kHz SCS, FFS details.
Agreement
If RAN1 decides that LBT is performed for S-SSB transmission, in addition to the S-SSB occasions in R16/R17 NR SL design, support additional candidate S-SSB occasions
· FFS the number and locations of additional candidate S-SSB occasions
· FFS when a UE transmits S-SSB on such additional candidate S-SSB occasions, and the related Rx UE’s behavior
R1-2207798 FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
Agreement
Regarding PSFCH transmission, at least the followings alternatives can be further studied
Agreement
If RAN1 decides that LBT is performed for PSFCH transmission, for the time and frequency domain locations of PSFCH resources, at least the followings alternatives can be further studied
Agreement
For S-SSB and synchronization in SL-U:
· No changes on R16 NR SL S-PSS/S-SSS sequence generation
· Continue studying the 4 options from the previous agreement and whether/how temporary exemption of OCB requirement is applicable for S-SSB transmission, e.g., how to meet the minimum of 2 MHz requirement under 15 kHz SCS
Agreement
For PSCCH and PSSCH resource indication in time/frequency domain:
Final summary in R1-2207799.
R1-2205841 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
R1-2205852 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2205888 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2205993 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2206043 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2206065 Discussion on co-channel coexistence for LTE sidelink and NR sidelink TOYOTA Info Technology Center
R1-2206099 Study on co-channel coexistence for LTE sidelink and NR sidelink ZTE,Sanechips
R1-2206121 Discussion on co-channel coexistence for LTE sidelink Sony
R1-2206292 Discussion on co-channel coexistence for LTE and NR V2X OPPO
R1-2206402 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2206440 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2206450 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2206471 Co-existence between LTE and NR sidelink NEC
R1-2206587 Considerations for LTE Sidelink and NR Sidelink Co-channel Coexistence Intel Corporation
R1-2206646 Discussion on co-channel coexistence for LTE and NR sidelink Xiaomi
R1-2206660 Discussion on Sidelink Co-channel Coexistence Panasonic
R1-2206671 Discussion of co-channel coexistence for LTE sidelink and NR sidelink Transsion Holdings
R1-2206681 Considerations on co-channel coexistence for LTE SL and NR SL CAICT
R1-2206692 Discussion on co-channel coexistence for LTE sidelink and NR sidelink China Telecom
R1-2206828 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2206915 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2206956 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2207010 Co-channel coexistence for NR sidelink and LTE sidelink MediaTek Inc.
R1-2207147 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2207154 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
R1-2207235 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated
R1-2207281 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2207339 Co-channel Coexistence for LTE Sidelink and NR Sidelink Apple
R1-2207410 Discussion on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2207509 Discussions on LTE and NR sidelink co-channel coexistence ROBERT BOSCH GmbH
R1-2207565 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2207601 Discussion on co-channel coexistence for LTE sidelink and NR sidelink WILUS Inc.
R1-2207625 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Continental Automotive GmbH
R1-2207636 FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Tuesday session
Working assumption
Co-channel coexistence between LTE SL and NR SL is supported for device type A. Device type A contains both LTE SL and NR SL modules. For device type A, the NR SL module may use the sensing and resource reservation information shared by the LTE SL module.
R1-2207670 FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Wed session
Conclusion
For co-channel coexistence in Rel-18, RAN1 concludes that the TDM-based semi-static resource pool partitioning based on Rel-16/17 specifications is one possible solution to ensure co-channel coexistence between LTE-V UEs and NR-V UEs.
· Note: The LTE and NR resource pools do not overlap in time with each other in the TDM-based semi-static resource pool partitioning.
· Note 2: Rel-16 in-device coexistence framework can ensure alignment between the slot boundary of the NR SL time slot and the subframe boundary of the LTE SL subframe
· FFS: potential enhancements for synchronization can be further investigated
Agreement
For co-channel coexistence in Rel-18, dynamic resource pool sharing is studied, with the following constraints:
· NR SL resource pool is configured with 15 kHz SCS.
o FFS support of NR SL resource pool configured with higher SCS, including other solutions to overcome the AGC issue caused by the differing SCSs between the NR SL and LTE SL resource pools
· For NR PSFCH (if configured), at least the following alternatives are studied:
o Alt 1: Avoid PSFCH transmission in time slots that overlap with subframes used for LTE SL transmissions.
§ FFS: Avoiding PSFCH transmissions can be performed by the UE transmitting PSFCH and/or the UE transmitting PSSCH.
o Alt 2: NR SL UEs use a periodically repeating set of PSFCH slots.
§ FFS: periodicities of the set.
Final summary in R1-2208096.
This agenda item was not treated in RAN1#110.
This agenda item was not treated in RAN1#110.
Please refer to RP-221938 for detailed scope of the WI.
R1-2210691 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
RAN1 study phase focusing on FR1 unlicensed bands (n46 and n96/n102) to be completed by RAN1#111.
Including evaluation methodology for unlicensed channel access (if any).
R1-2208356 On Channel Access Mechanism for SL-U Nokia, Nokia Shanghai Bell
R1-2208370 Discussion on channel access mechanism for sidelink on unlicensed spectrum FUTUREWEI
R1-2208448 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2208554 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2208643 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2208722 Discussion on channel access mechanism for SL-U ZTE, Sanechips
R1-2208822 On channel access mechanism and resource allocation for SL-U OPPO
R1-2208976 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2209017 Discussion on channel access mechanism for SL-U Fujitsu
R1-2209054 Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2209081 Discussion on channel access mechanisms Johns Hopkins University APL
R1-2209101 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2209148 Channel Access of Sidelink on Unlicensed Spetrum NEC
R1-2209167 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2209236 Considerations on channel access mechanism of SL-U CAICT
R1-2209286 Discussion on channel access mechanism for sidelink-unlicensed xiaomi
R1-2209301 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2209338 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2209404 Discussion on channel access mechanism for sidelink on unlicensed spectrum ETRI
R1-2209417 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2209478 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
R1-2209529 Discussion on channel access mechanism MediaTek Inc.
R1-2210271 SL-U Simulation assumption parameters CableLabs, Broadcom, Hewlett-Packard Enterprise, Cisco (rev of R1-2209551)
R1-2209585 Channel access mechanism for sidelink on FR1 unlicensed band Apple
R1-2209646 Further Details of Channel Access Mechanism National Spectrum Consortium
R1-2209659 SL Channel access in unlicensed spectrum InterDigital, Inc.
R1-2209731 On channel access mehanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2209767 On Channel Access Mechanism for SL-U ITL
R1-2209775 Discussion on Channel access mechanism for NR sidelink evolution Sharp
R1-2209780 Sidelink channel access on unlicensed spectrum Panasonic
R1-2209904 Discussion on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2209985 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2210074 Discussion on sidelink on unlicensed spectrum ASUSTeK
R1-2210082 Discussions on channel access mechanism for sidelink on unlicensed spectrum ROBERT BOSCH GmbH
R1-2210132 Channel access mechanism for SL-U Ericsson
R1-2210139 Discussion on channel access mechanism for SL on unlicensed spectrum WILUS Inc.
[110bis-e-R18-SL-01] – Kevin (OPPO)
Email discussion on channel access mechanism for unlicensed spectrum by October 19
- Check points: October 14, October 19
R1-2210289 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
Presented in Oct 10th GTW session
R1-2210290 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Oct 13th GTW session
Agreement
· Type 1 SL channel access procedure is applicable to the following transmissions by a UE:
o PSSCH/PSCCH transmission(s) scheduled or configured by a gNB in SL Mode 1 resource allocation.
o PSSCH/PSCCH transmission(s) from the UE in SL Mode 2 resource allocation.
o Other SL transmissions including S-SSB and PSFCH transmissions from a UE
§ FFS: how to set CAPC for S-SSB and PSFCH
o Note: Type 1 can be used to initiate a COT
· A UE uses a channel access priority class applicable to the sidelink user plane data multiplexed in PSSCH for performing the Type 1 channel access procedures to transmit transmission(s) including PSSCH with user plane data and its associated PSCCH.
o Note: how to set CAPC for MAC CE multiplexed in PSSCH is up to RAN2
· A UE shall not transmit on a channel for a Channel Occupancy Time that exceeds the maximum COT duration where the channel access procedures are performed based on a channel access priority class p associated with the UE transmissions, as given in CAPC table for SL.
Agreement
On the support of MCSt operation in SL-U, following options are to be further studied and one or more of the following options will be selected in future meetings.
· When L1 is triggered for reporting a subset of candidate resources for MCSt,
o Option
1: Only one set of parameters (
, remaining PDB, 
and 
) is provided for
the resource selection procedure in L1
§ Note, this is applicable for transmission of a single TB and multiple TBs
§ FFS: whether this is the same or different than Rel-16
o Option
2: one or multiple sets of parameters (, remaining PDB, and ) are provided for
the resource selection procedure in L1
o FFS: any further information needs to be provided to L1 for MCSt
· When L1 reports a subset of candidate resources for MCSt,
o Option A: L1 reports candidate multi-slot resources in SA where a candidate multi-slot resource consists of a set of single-slot resources that are consecutive in time
§ FFS whether the
set of single-slot resources within a candidate multi-slot resource can have
different sizes
o Option B: L1 reports candidate single-slot resources in (SA) as in Rel-16
§ It is up to the higher (MAC) layer to select a set of single-slot resources that are consecutive in logical slots
o Option C: L1 reports consecutive single-slot candidate resources in SA
§ FFS whether the
consecutive single-slot candidate resources can have different sizes
o FFS: any further information needs to be reported to MAC layer, provided to L1 or utilized for MCSt
o FFS: whether/how to consider the additional LBT time in SL resource allocation
R1-2210291 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2210292 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Oct 18th GTW session
Agreement
For dynamic channel access mode with multi-channel case in SL-U, NR-U UL channel access procedure is considered as baseline for transmission on multiple channels
· FFS: whether transmission of PSFCH and/or S-SSB on a subset of RB sets is supported (using the NR-U DL channel access procedure as baseline)
· FFS any necessary enhancement and modification for the SL-U operation
R1-2210709 FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Oct 19th GTW session
Agreement
In Type 1 SL channel access procedure, the following table is adopted for channel access priority class (CAPC) for SL.
· FFS: the applicability and usage of NOTE1 in the table
· FFS: whether mp=1 can be used with p=1, and applicable cases
|
Channel Access Priority Class (p) |
mp |
CWmin,p |
CWmax,p |
Tslmcot,p |
allowed CWp sizes |
|
1 |
2 |
3 |
7 |
2 ms |
{3,7} |
|
2 |
2 |
7 |
15 |
4 ms |
{7,15} |
|
3 |
3 |
15 |
1023 |
6ms [or 10 ms] |
{15,31,63,127,255,511,1023} |
|
4 |
7 |
15 |
1023 |
6ms [or 10 ms] |
{15,31,63,127,255,511,1023} |
|
[NOTE1: Forp=3,4, Tslmcot,p=10ms if the higher layer parameter absenceOfAnyOtherTechnology-r14 or absenceOfAnyOtherTechnology-r16 is provided, otherwise,Tslmcot,p=6ms.] NOTE 2: When Tslmcot,p=6ms it may be increased to 8ms by inserting one or more gaps. The minimum duration of a gap shall be 100μs. The maximum duration before including any such gap shall be 6ms. |
|||||
Agreement
, use the latest 
used for any SL
transmissions on the channel using Type 1 channel access procedures
associated with the channel access priority class 
. is consecutively
used 
times for
generation of 
, is updated for
each priority class to the next
higher allowed value. for every
priority class to the next
higher allowed value. is reset to 
for every
priority class , otherwise increase for every
priority class to the next
higher allowed value. 
; otherwise 
is increased., use the latest used for any SL
transmissions on the channel using Type 1 channel access procedures
associated with the channel access priority class . for every
priority class to the next
higher allowed value. is reset to 
for every
priority class ., use the latest used for any
SL transmissions on the channel using Type 1 channel access procedures
associated with the channel access priority class . , otherwise is increased, otherwise
is increased. ; otherwise is increased.
Final summary in R1-2210293.
R1-2208357 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2208371 Discussion on physical channel design for sidelink on unlicensed spectrum FUTUREWEI
R1-2208449 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2208492 Discussion on physical channel design of Sidelink on unlicensed spectrum Quectel
R1-2208555 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2208644 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2208723 Discussion on physical layer structures and procedures for SL-U ZTE, Sanechips
R1-2208823 On PHY channel designs and procedures for SL-U OPPO
R1-2208977 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2209055 Physical Channel Design for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2209083 Discussion on physical channel design framework Johns Hopkins University APL
R1-2209102 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2209149 Discussion on physical channel design framework NEC
R1-2209168 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2209202 Discussion on Physical channel design framework for sidelink on unlicensed spectrum Hyundai Motor Company
R1-2209287 Discussion on physical channel design for sidelink-unlicensed xiaomi
R1-2209302 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2209339 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2209405 Discussion on physical channel design framework for SL-U ETRI
R1-2209418 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2209479 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2209530 Discussion on physical channel design framework MediaTek Inc.
R1-2209586 Discussion on Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum Apple
R1-2209647 Physical Channel Design Considerations National Spectrum Consortium
R1-2209660 SL U physical layer design framework InterDigital, Inc.
R1-2209732 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
R1-2209773 On Physical Channel Design framework for SL-U ITL
R1-2209776 Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2209781 Physical channel design for sidelink on unlicensed spectrum Panasonic
R1-2209905 Discussion on channel design framework in SL-U NTT DOCOMO, INC.
R1-2209986 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2210044 Physical channel design for sidelink on unlicensed spectrum EURECOM
R1-2210133 PHY channel design framework for SL-U Ericsson
R1-2210140 Discussion on PHY channel design framework for SL on unlicensed spectrum WILUS Inc.
[110bis-e-R18-SL-02] – Mixiang (Huawei)
Email discussion on physical channel design framework for unlicensed spectrum by October 19
- Check points: October 14, October 19
R1-2210252 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Oct 10th GTW session
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U:
· Regarding 1 sub-channel equals K interlace(s)
o At least K=1 and K=2 is supported for 15 kHz SCS
o At least K=1 is supported for 30 kHz SCS
o FFS: details related to multiple RB sets
R1-2210253 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
R1-2210254 FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Oct 14th GTW session
Working assumption:
Support maximum 2 candidate starting symbols within a slot for a PSCCH/PSSCH transmission.
· RAN1 strives to have unified design for PSCCH/PSSCH transmission from 1st or 2nd starting symbol
· The candidate starting symbol(s) are intended for AGC purpose
· FFS: other potential uses of the candidate starting symbol(s)
· FFS other details, e.g., applicable scenarios (including SCS), position of 2nd starting symbol, TBS determination, PSCCH blind decoding complexity, processing time constraints, etc.
· FFS whether 2 candidate starting symbols is also supported for slots with PSFCH
Agreement
To meet OCB and PSD requirement for S-SSB transmission, down-select between the followings for 15 kHz and 30 kHz SCS:
· Option 1: Using interlaced RB transmission for S-PSS/S-SSS/PSBCH
· Option 3: Repetition of S-PSS/S-SSS/PSBCH in frequency domain
· FFS: whether/how the above options apply to all or subset of channel type of S-PSS/S-SSS/PSBCH
· Note: RAN1 further study the relationship between above options and temporary OCB exemption, and the discussion on temporary OCB exemption can continue even if option 1 or option 3 is supported
FFS: how to handle 60 kHz SCS (if needed, not limited to option 1 or option 3)
R1-2210255 FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Oct 18th GTW session
Agreement
Regarding frequency domain resource indication for interlace RB-based PSSCH transmission:
· When more than one RB set is used for transmissions, down-select one of the followings
o Option A: Support that the used interlace index(s) in different RB sets are always the same
o Option B: Support that the used interlace index(s) in different RB sets can be different
· FFS details
Agreement
Regarding frequency domain resource indication for interlace RB-based PSSCH transmission:
· Down-select one of the followings
o Option 1: Support explicitly indicating the used sub-channel index(s) and RB set index(s)
o Option 2: Support explicitly indicating at least the used sub-channel index(s)
§ At least RB set index(s) is not explicitly indicated
· FFS details
Agreement
For PSCCH and PSSCH in SL-U:
· PSCCH is transmitted within 1 sub-channel
· At least support Option 1 below
o Option 1: PSCCH locates in the lowest sub-channel of lowest RB set of corresponding PSSCH
§ Note: the lowest sub-channel may not be entirely contained in the lowest RB set
· FFS whether/how to handle the case where UEs supporting different bandwidths can use the same resource pool to communicate with each other, e.g., whether/how to additionally support Option 2 below
o Option 2: PSCCH locates in every RB set of corresponding PSSCH
· Note: the above options do not imply any restriction on the mapping of sub-channels to PRBs.
· FFS other details
Agreement
Regarding usage of PRBs within intra-cell guard band of two adjacent RB sets:
Agreement
At least R16/R17 NR SL S-SSB slots are excluded from SL resource pool.
· Note: whether or not additional candidate S-SSB occasions are excluded from resource pool will be discussed after the details of additional candidate S-SSB occasions are clearer
Decision: As per email decision posted on Oct 20th,
At least there is 1 PSFCH occasion per PSCCH/PSSCH transmission, FFS details
Agreement
To address PSFCH transmission dropping due to LBT failure, the followings are to be studied:
· Alt 1: Support more than 1 PSFCH occasion per PSCCH/PSSCH transmission
· Alt 2: PSFCH resources are dynamically indicated
· Alt 3: Convey SL-HARQ feedback information in PSCCH/PSSCH, e.g., new SCI or new MAC-CE
· Alt 4: drop PSFCH transmission
· Alt 5: Support trigger based HARQ feedback reporting for non-numerical HARQ FB and one shot HARQ FB
· Combination of above alternatives are not precluded
· FFS details of above alternatives
Agreement
Regarding additional candidate S-SSB occasions:
· Their number and time domain locations are (pre-)configured or pre-defined
Final summary in R1-2210256.
Consider additional RAN guidance on co-channel coexistence in RP-222674.
R1-2208358 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
R1-2208450 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2208556 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2208645 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2208724 Study on co-channel coexistence for LTE sidelink and NR sidelink ZTE, Sanechips
R1-2208765 Discussion on Sidelink Co-channel Coexistence Panasonic
R1-2208824 Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL OPPO
R1-2208978 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2209056 Considerations for LTE Sidelink and NR Sidelink Co-channel Coexistence Intel Corporation
R1-2209103 Discussion on co-channel coexistence for LTE sidelink Sony
R1-2209150 Co-existence between LTE and NR sidelink NEC
R1-2209169 Discussion of co-channel coexistence for LTE sidelink and NR sidelink Transsion Holdings
R1-2209237 Considerations on co-channel coexistence for LTE SL and NR SL CAICT
R1-2209288 Discussion on co-channel coexistence for LTE and NR sidelink xiaomi
R1-2209303 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2209340 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2209406 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2209419 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2209480 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2209520 Co-channel coexistence for NR sidelink and LTE sidelink MediaTek Inc.
R1-2209587 Discussion on Co-channel Coexistence for LTE Sidelink and NR Sidelink Apple
R1-2209611 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
R1-2209632 Discussion on dynamic co-channel coexistence for LTE sidelink and NR sidelink TOYOTA Info Technology Center
R1-2209637 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2209733 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2209777 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2209906 Discussion on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2210397 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated (rev of R1-2209987)
R1-2210080 Views on LTE and NR sidelink co-channel coexistence ROBERT BOSCH GmbH
R1-2210131 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2210141 Discussion on co-channel coexistence for LTE sidelink and NR sidelink WILUS Inc.
R1-2210187 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Continental Automotive GmbH
[110bis-e-R18-SL-03] – Sarun (Fraunhofer)
Email discussion on co-channel coexistence for LTE-NR SL by October 19
- Check points: October 14, October 19
R1-2210294 FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Oct 11th GTW session
Agreement
For dynamic resource pool sharing, the candidate information shared by the LTE SL module to the NR SL module may include one or more of the following parameters, to be down-selected:
· Time and frequency locations of reserved resources by other LTE UEs, determined based on decoded SCIs
· SL RSRP measurement results
· Resource reservation periods based on decoded SCI and for own LTE SL transmissions
· Priority based on decoded SCI and for own LTE SL transmissions
· Time and frequency location of resources used for own LTE SL transmissions
· Candidate resource set SA or SB
· SL RSSI measurements
· LTE logical subframe related information
· Resources corresponding to half-duplex subframes which are not monitored by the LTE SL UE
Agreement
For dynamic resource pool sharing, the NR SL module uses the information shared by the LTE SL module to the NR SL module to determine the set of resources for its own transmission.
· FFS: which layer carries out the resource determination: PHY layer or MAC layer.
R1-2210295 FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
R1-2210296 FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Oct 14th GTW session
Agreement
· For dynamic resource pool sharing, where the NR SL module uses the candidate information shared by the LTE SL module to the NR SL module, continue studying the following alternatives:
o Alt 1: The LTE SL module provides the NR SL module with the candidate information (excluding at least the candidate resource sets SA or SB)
§ The NR SL module identifies a set of resources based on information shared by the LTE SL module.
· FFS: how to identify the set of resources
§ The NR SL module excludes these identified resources from its own candidate resource set when performing the resource (re)selection procedure.
§ The exclusion process is performed in the PHY layer.
§ Note: implementation of Alt 1 should not have specification impact to LTE
o Alt 2: The LTE SL module provides the NR SL module with the candidate resource sets SA or SB shared by the LTE SL module
§ The LTE PHY SL module is provided information from the higher layer to generate a candidate resource set SA or SB. The resource set SA or SB is then shared to NR SL module.
§ The NR SL module performs an intersection operation with the candidate resource set received from the LTE SL module and the candidate resource set generated by the NR SL module.
· FFS: how to handle the case where this results in an insufficient set of resources
§ The intersection operation is performed in the MAC layer.
§ FFS: How to handle NR V2X parameter settings that are not supported by LTE V2X, e.g., periodicities, sub-channel sizes, etc
§ Note: implementation of Alt 2 should not have specification impact to LTE
o In the next meeting strive to decide between the two alternatives
R1-2210297 FL Summary #4 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Oct 19th GTW session
Agreement
For dynamic resource pool sharing, the NR SL module is expected to use the information shared by the LTE SL module to the NR SL module which is known by NR SL module at the latest T ms prior to slot n (as defined in clause 8.1.4 of TS 38.214), to determine a set of resources for its own (re)transmission.
· T is defined using
o T≤Tmax ms, and is based on UE implementation, according to the Rel-16 NR SL timeline for in-device coexistence.
§ FFS: Value of Tmax
· FFS: any discussion on the earliest information, if needed
Final summary in R1-2210298.
Focus only on updating the evaluation methodology for commercial deployment scenario in RAN1#110bis-e and RAN1#111.
R1-2208359 On Evaluation Methodology for Sidelink in FR2 Nokia, Nokia Shanghai Bell
R1-2208451 Evaluation methodology for sidelink operation on FR2 licensed spectrum Huawei, HiSilicon
R1-2208557 Discussion on enhanced sidelink operation on FR2 licensed spectrum Spreadtrum Communications
R1-2208646 Enhanced sidelink operation on FR2 licensed spectrum vivo
R1-2208725 Discussion on the evaluation methodology for SL on FR2 ZTE, Sanechips
R1-2208825 On updating evaluation methodology for SL operation in FR2 OPPO
R1-2208979 Discussion on the evaluation methodology for enhanced sidelink operation on FR2 licensed spectrum CATT, GOHIGH
R1-2209057 Evaluation Methodologies for SL Operating in FR-2 licensed band Intel Corporation
R1-2209082 Discussion on evaluation methodology for commercial deployment scenario Johns Hopkins University APL
R1-2209289 Discussion on updating the evaluation methodology for commercial deployment scenario xiaomi
R1-2209304 Discussion on evaluation methodology for sidelink on FR2 Lenovo
R1-2209407 Discussion on evaluation methodology for enhanced SL operation on FR2 ETRI
R1-2209481 Discussion on evaluation methodology for sidelink on FR2 licensed spectrum LG Electronics
R1-2209531 Discussion on evaluation methodology for SL FR2 licensed spectrum MediaTek Inc.
R1-2209588 Evaluation Methodology for Sidelink Operation on FR2 Licensed Spectrum Apple
R1-2209638 On enhanced SL FR2 operation InterDigital, Inc.
R1-2209734 Evaluation Methodology for Enhanced SL Operation in FR2 Samsung
R1-2209988 Enhanced sidelink operation on FR2 licensed spectrum Qualcomm Incorporated
R1-2210110 Discussion on evaluation methodology for beam enhancement on sidelink FR2 operation CEWiT
R1-2210134 Evaluation methodology for sidelink in FR2 Ericsson
[110bis-e-R18-SL-04] – Chunxuan (Apple)
Email discussion on SL operation for FR2 by October 19
- Check points: October 14, October 19
R1-2210262 FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Oct 11th GTW session
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2
· Reuse indoor layout defined for SL-U with pairs topology and without WiFi nodes
o FFS: total number of UEs deployed in the layout
o Companies should report how UEs are paired
· FFS: whether to consider the cluster-based topology defined for SL-U
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, reuse layout option 3 in Section A.2.1.1 of TR 36.843 with
R1-2210331 FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Oct 14th GTW session
Agreement
For the indoor layout defined in the evaluation methodology for commercial deployment scenario for sidelink operation on FR2, the total number of UEs is 12 pairs/20 MHz with scaling factors of 1, ˝ or 1/3.
Agreement
For the outdoor layout defined in the evaluation methodology for commercial deployment scenario for sidelink operation on FR2, the number of UEs per cell is 60 with scaling factors of 1, ˝ or 1/3.
Agreement
For the outdoor layout defined in the evaluation methodology for commercial deployment scenario for sidelink operation on FR2, Uu link has different carrier as PC5 in the simulation is the baseline.
· Optional: Uu link has same carrier as PC5 in the simulation.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, for the outdoor layout, the channel model reuses the procedures and parameters for UMi - Street Canyon specified in TR 38.901.
Decision: As per email decision posted on Oct 15th,
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, for the indoor layout, the channel model reuses the procedures and parameters for InH mixed office specified in TR 38.901.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, for UE antenna parameters, reuse the antenna element pattern and antenna array configuration for pedestrian UE and cellular UE as in Table 6.1.4-6 and Table 6.1.4-7 of TR 37.885.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, consider at least the following parameters:
· Carrier frequency: 30 GHz
· Sub-carrier spacing: 120 kHz (baseline), 60 kHz (optional)
· Simulation bandwidth: 100 MHz (baseline), 200 MHz (optional)
· UE receiver noise figure: 13 dB (baseline), 10 dB (optional)
· UE Tx power: 23 dBm (EIRP should not exceed 43 dBm)
· UE speed: 3 km/h
Agreement
For the outdoor layout defined in the evaluation methodology for commercial deployment scenario for sidelink operation on FR2, ISD is 200 meters.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, support at least the following traffic model:
Decision: As per email decision posted on Oct 18th,
Agreement
When reporting the simulation results for sidelink operation on FR2, companies should report the used resource allocation scheme.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, performance metric includes UPT, latency and PRR which regards the packet whose delay exceeding the remaining PDB as transmission failure.
· FFS: UE satisfaction as section 7.2 in TR 38.838 for XR traffic evaluation
Final summary in R1-2210425.
Placeholder only. No contributions in RAN1#110bis-e and RAN1#111.
Please refer to RP-221938 for detailed scope of the WI.
R1-2212846 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
Endorsed and contents incorporated below.
[111-R18-SL] – Kevin (OPPO)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
RAN1 study phase focusing on FR1 unlicensed bands (n46 and n96/n102) to be completed by RAN1#111.
Including evaluation methodology for unlicensed channel access (if any).
From AI 5
R1-2210805 LS on SL LBT failure indication and consistent SL LBT failure RAN2, vivo
R1-2212827 Moderator summary of discussion for LS reply on SL LBT failure indication and consistent SL LBT failure Moderator (vivo)
R1-2212828 Draft reply LS on SL LBT failure indication and consistent SL LBT failure Moderator (vivo)
No consensus on sending an LS to RAN2.
R1-2210827 On Channel Access Mechanism for SL-U Nokia, Nokia Shanghai Bell
R1-2210835 Channel access mechanism for sidelink on unlicensed spectrum FUTUREWEI
R1-2210891 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2211007 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2211079 Discussion on channel access mechanism for SL-U Fujitsu
R1-2211198 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2211235 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2211263 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
R1-2211364 Discussion on channel access mechanism for sidelink-unlicensed xiaomi
R1-2211400 Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2211450 On channel access mechanism and resource allocation for SL-U OPPO
R1-2211514 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2211560 Discussion on channel access mechanism for sidelink on unlicensed spectrum ETRI
R1-2211579 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2211612 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2211682 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2211709 Sidelink channel access on unlicensed spectrum InterDigital, Inc.
R1-2212521 SL-U Channel Access Mechanism Details CableLabs (rev of R1-2211758)
R1-2211761 Further Discussion on Channel Access Mechanisms Johns Hopkins University APL
R1-2211814 On channel access mechanism for sidelink on FR1 unlicensed spectrum Apple
R1-2211917 Considerations on channel access mechanism of SL-U CAICT
R1-2211985 Discussion on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2212045 On channel access mechanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2212117 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2212184 Discussion on Channel access mechanism for NR sidelink evolution Sharp
R1-2212206 Discussion on channel access mechanism for SL-U ZTE, Sanechips
R1-2212222 Channel access mechanism for SL-U Ericsson
R1-2212270 Discussion on channel access mechanism MediaTek Inc.
R1-2212274 Sidelink channel access on unlicensed spectrum Panasonic
R1-2212287 Channel Access Mechanism for SL-U ITL
R1-2212363 Channel Access of Sidelink on Unlicensed Spectrum NEC
R1-2212439 Discussion on channel access mechanism for SL-U WILUS Inc.
R1-2212442 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2212681 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Nov 14th session
Agreement
· Type 2A channel access procedure is applicable for S-SSB transmissions from a UE without a shared channel occupancy, when the following constraints are met:
o Time duration is at most 1ms per transmission
o The duty cycle of the S-SSB transmissions is at most 1/20
o FFS: details of EDT
o FFS: whether/how to define observation period, including whether or not observation period would be captured in the specifications if defined
· FFS: Type 2A applicability for PSFCH without a shared channel occupancy and further limitations for combined transmissions of both S-SSB and PSFCH using Type 2A channel access procedure
R1-2212682 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2212683 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2212684 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Nov 16th session
Agreement
R1-2212685 FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2212801 FL summary #6 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Nov 17th session
Agreement
· A CPE is transmitted from a CPE starting position before SL transmission within a COT, select one or both of the two options:
o Option 1: within the symbol just before the next AGC symbol
o Option 2: within at most 1, 2 or 4 symbols just before the next AGC symbol for 15, 30 or 60 kHz SCS, respectively
o FFS: whether Option 1 and Option 2 are both applicable and the conditions (e.g., Option 1 in case of COT sharing and Option 2 in case of initiating a COT)
o FFS: which channel access type(s) is applicable for option 1 and option 2
o FFS: other details
· A single CPE starting position for PSFCH
o FFS CPE starting position and whether it should be (pre-)configured in each RP, pre-defined or indicated
o FFS other details (e.g., indication granularity)
o Note: value 0 is a candidate
· At least one CPE starting position for S-SSB
o FFS CPE starting position should be (pre-)configured, pre-defined or indicated
o FFS: Whether multiple CPE starting positions should be (pre-)configured, pre-defined or indicated
o FFS CPE starting positions for the R16 S-SSB and the additional S-SSBs
o Note: value 0 is a candidate
· One or multiple CPE starting positions can be (pre-)configured in each resource pool for PSSCH/PSCCH
o When multiple CPE starting positions are (pre-)configured,
§ FFS whether/how to define a criteria for selecting a default CPE starting position (e.g., according to partial/full RB set allocation, resource reservation information, within or outside of a COT, etc.)
§ FFS criteria for selecting one of the multiple CPE starting positions (e.g., according to priority level (e.g., CAPC or L1), selected randomly by UE from the (pre-)configured set of CPEs, selected by the UE based on channel access result, determined based on indication from the COT initiating UE, etc.)
o FFS other details
R1-2212802 FL summary #7 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Nov 18th session
Agreement
For UE-to-UE COT sharing,
· When performing S-SSB transmission(s), a responding UE can utilize a COT shared by a COT initiating UE (using type 1 channel access) when the responding UE is intended to transmit S-SSB within RB set(s) corresponding to the shared COT.When performing PSFCH transmission(s), a responding UE can utilize a COT shared by a COT initiating UE at least when at least one of the responding UE’s PSFCH transmissions in a symbol/slot within RB set(s) corresponding to the shared COT is intended for the COT initiating UE.
o FFS: whether a responding UE can transmit PSFCH(s) to UE(s) other than the initiator
· When performing PSSCH/PSCCH transmission(s), a responding UE can utilize a COT shared by a COT initiating UE at least when the responding UE’s PSSCH/PSCCH transmission(s) within RB set(s) corresponding to the shared COT is intended for the COT initiating UE
o FFS whether to support the case if a responding UE transmits PSSCH/PSCCH to destination ID other than the source ID of the COT initiating transmission, where the destination ID of the responding UE’s PSSCH/PSCCH transmission(s) can be different from the source/destination IDs of COT initiating UE’s PSSCH/PSCCH transmission when sharing the COT information.
§ FFS: how to determine / what are the restrictions to the destination ID of the responding UE’s PSSCH/PSCCH transmission(s) to utilize the COT shared by the initiating UE.
§ FFS whether the responding UE can utilize the COT when at least the responding UE’s PSCCH transmission in the reserved resources within the shared COT or MCSt is intended for the COT initiating UE and what are the restrictions (e.g., priority, etc.) and indication to the responding UE.
· FFS: UE forwarding/relaying information about a COT initiated by another UE.
Agreement
, the next higher allowed
value for adjusting 
is 
. is consecutively used 
times for generation of 
, is reset to 
only for that priority class 
for which is consecutively used times for generation of . is selected by UE from the
set of values {1, 2, …,8} for each priority class 
.
R1-2212803 FL summary #8 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2212686 FL summary for AI 9.4.1.1: SL-U channel access mechanism (EOM) Moderator (OPPO)
R1-2210828 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2210836 Physical channel design for sidelink on unlicensed spectrum FUTUREWEI
R1-2210892 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2211008 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2211113 Discussion on Physical channel design framework for sidelink on unlicensed spectrum Hyundai Motor Company
R1-2211199 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2211236 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2211264 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2211365 Discussion on physical channel design for sidelink-unlicensed xiaomi
R1-2211401 Physical Layer Enhancements for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2211451 On PHY channel designs and procedures for SL-U OPPO
R1-2211515 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2211561 Discussion on physical channel design framework for SL-U ETRI
R1-2211580 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2211613 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2211683 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2211710 SL U physical layer design framework InterDigital, Inc.
R1-2211762 Further Discussion on Physical Channel Design Framework Johns Hopkins University APL
R1-2211815 On Physical Channel Design Framework for Sidelink on FR1 Unlicensed Spectrum Apple
R1-2211986 Discussion on channel design framework in SL-U NTT DOCOMO, INC.
R1-2212046 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
R1-2212118 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2212185 Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2212207 Discussion on physical layer structures and procedures for SL-U ZTE, Sanechips
R1-2212223 PHY channel design framework for SL-U Ericsson
R1-2212271 Discussion on physical channel design framework MediaTek Inc.
R1-2212277 Physical channel design for sidelink on unlicensed spectrum Panasonic
R1-2212288 Physical Channel Design framework for SL-U ITL
R1-2212356 Discussion on physical channel design framework NEC
R1-2212440 Discussion on PHY channel design framework for SL-U WILUS Inc.
R1-2212443 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2212645 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
R1-2212646 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Nov 14th session
Agreement
For slots with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
Agreement
If a resource pool includes slots with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
Agreement
Regarding PSFCH transmission under 15 kHz and 30 kHz SCS, RAN1 continues studying the following updated alternatives:
Agreement
Slots with PSFCH symbols only have 1 candidate starting symbol for PSCCH/PSSCH.
R1-2212647 FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Nov 16th session
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U:
· Regarding mapping between sub-channel and interlace, RAN1 further study the followings:
o Option 1: 1 sub-channel is defined and indexed within 1 RB set, and is periodically indexed across different RB sets within the resource pool
o Option 2: 1 sub-channel is defined within 1 RB set, and is incrementally indexed firstly within an RB set, then across different RB sets within the resource pool
o Option 3: 1 sub-channel is defined across all RB sets within the resource pool, i.e., 1 sub-channel includes K interlace(s) across all RB sets within the resource pool
o Option 4: 1 sub-channel is defined within 1 RB set or 2 adjacent RB sets, and is incrementally indexed firstly within an RB set, then across different RB sets within the resource pool
o Option 5: 1 sub-channel is defined within 1 RB set, and is incrementally indexed firstly across different RB sets within the resource pool, then across different interlaces in the RB set
o FFS: whether/how to use intra-cell guardband PRBs
Agreement
For S-SSB transmission, down-select one or more of the following for 15 kHz and 30 kHz SCS:
· Option 1-1: Using interlaced RB transmission for all of S-PSS/S-SSS/PSBCH
· Option 1-2: Using interlaced RB transmission for PSBCH only, and apply OCB exemption to S-PSS and S-SSS
· Option 3-1: Repeat S-PSS/S-SSS/PSBCH N times in frequency domain, and there is a gap between the repetition(s) to meet OCB requirement
o FFS details, e.g., the length of gap is (pre-)configured or pre-defined, value of N (e.g., N=2)
o FFS gap of 0
· Option 3-2: Repeat only S-PSS/S-SSS K times in frequency domain, and PSBCH is rate matched. There is a gap between the repetition(s) to meet OCB requirement
o FFS details, e.g., the length of gap is (pre-)configured or pre-defined, value of K
o FFS gap of 0
o FFS PSBCH resource
· Option 3-3: keep the legacy S-PSS/S-SSS/PSBCH while repeating PSBCH N times in frequency domain and rate-matching PSBCH to S-PSS/S-SSS symbols, and there is a gap between the PSBCH repetition(s) to meet OCB requirements
o FFS details, e.g. the length of gap is (pre-)configured or pre-defined, value of N
· Option A: Apply OCB exemption to all of S-PSS/S-SSS/PSBCH
· For Option 1-1 and 1-2 above
o FFS: whether/how to handle the case when each interlace has only 10 PRBs in a RB set
· FFS: whether transient period issue exists and whether/how to address it
R1-2212648 FL summary#4 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Nov 17th session
Agreement
For a slot with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
Agreement
To address PSFCH transmission dropping due to LBT failure, RAN1 down-select one of followings, or support the combination of followings:
Agreement
Regarding the number and location(s) of additional candidate S-SSB occasions, RAN1 further study the followings:
Agreement
Regarding additional candidate S-SSB occasions:
Agreement
For contiguous RB-based PSCCH/PSSCH transmission in SL-U:
Agreement
Regarding PSFCH transmission under 60 kHz SCS, further study the following alternatives:
Agreement
Regarding S-SSB, RAN1 further study the following:
· How to transmit S-SSB when a SL BWP contains multiple RB sets.
Final summary in R1-2212649.
Consider additional RAN guidance on co-channel coexistence in RP-222674.
R1-2210829 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
R1-2210839 Dynamic coexistence between NR and LTE sidelink FUTUREWEI
R1-2210893 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2211009 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2211200 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2211237 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2211265 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2211300 Dynamic co-channel coexistence for LTE sidelink and NR sidelink TOYOTA Info Technology Center, Continental Automotive Technologies GmbH
R1-2211366 Discussion on co-channel coexistence for LTE and NR sidelink xiaomi
R1-2211402 Design Considerations for LTE and NR Sidelink Co-Channel Coexistence Intel Corporation
R1-2211452 Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL OPPO
R1-2211516 Discussion of co-channel coexistence for LTE sidelink and NR sidelink Transsion Holdings
R1-2211562 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2211581 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2211614 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sony
R1-2211684 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2211724 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2211816 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Apple
R1-2211840 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
R1-2211987 Discussion on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2212047 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2212119 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated
R1-2212186 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2212196 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ASUSTeK
R1-2212208 Study on co-channel coexistence for LTE sidelink and NR sidelink ZTE, Sanechips
R1-2212221 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2212258 Sidelink co-channel coexistence MediaTek Inc.
R1-2212279 Discussion on Sidelink Co-channel Coexistence Panasonic
R1-2212322 Discussion on LTE and NR sidelink co-channel coexistence ROBERT BOSCH GmbH
R1-2212364 Co-existence between LTE and NR sidelink NEC
R1-2212441 Discussion on co-channel coexistence for LTE sidelink and NR sidelink WILUS Inc.
R1-2212444 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2212537 FL Summary #1 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
R1-2212538 FL Summary #2 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
R1-2212539 FL Summary #3 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Nov 15th session
Agreement
Based on the agreement in RAN1#110bis-e, the value of Tmax = 4 ms.
R1-2212769 FL Summary #4 of AI 9.4.2 - Co-channel coexistence for LTE sidelink and NR sidelink Moderator (Fraunhofer HHI)
From Nov 17th session
Agreement
For dynamic resource pool sharing, the NR SL module uses the candidate information shared by the LTE SL module to the NR SL module, where
Final summary in R1-2212540.
Focus only on updating the evaluation methodology for commercial deployment scenario in RAN1#110bis-e and RAN1#111.
R1-2210830 On Evaluation Methodology for Sidelink in FR2 Nokia, Nokia Shanghai Bell
R1-2210894 Remaining issues on evaluation methodology for sidelink operation on FR2 licensed spectrum Huawei, HiSilicon
R1-2211010 Enhanced sidelink operation on FR2 licensed spectrum vivo
R1-2211201 Discussion on the evaluation methodology for enhanced sidelink operation on FR2 licensed spectrum CATT, GOHIGH
R1-2211266 Discussion on evaluation methodology for sidelink on FR2 licensed spectrum LG Electronics
R1-2211367 Discussion on updating the evaluation methodology for commercial deployment scenario xiaomi
R1-2211403 Remaining Details for the Evaluation Methodology for SL Operating in FR-2 Licensed Band Intel Corporation
R1-2211453 Discussion On remaining issues of evaluation methodology for SL operation in FR2 OPPO
R1-2211563 Discussion on evaluation methodology for enhanced SL operation on FR2 ETRI
R1-2211582 Discussion on evaluation methodology for sidelink on FR2 Lenovo
R1-2211727 On enhanced SL FR2 operation InterDigital, Inc.
R1-2211760 Further discussion on antenna model enhancements for evaluation methodology for commercial deployment scenario Johns Hopkins University APL
R1-2211817 Discussion on Evaluation Methodology for Sidelink Operation on FR2 Licensed Spectrum Apple
R1-2212048 Evaluation Methodology for Enhanced SL Operation in FR2 Samsung
R1-2212120 Enhanced sidelink operation on FR2 licensed spectrum Qualcomm Incorporated
R1-2212209 Further update on the evaluation methodology for SL on FR2 ZTE, Sanechips
R1-2212224 Evaluation methodology for sidelink in FR2 Ericsson
R1-2212269 Discussion on evaluation methodology for SL FR2 licensed spectrum MediaTek Inc.
R1-2212426 Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation CEWiT
R1-2212582 FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Nov 15th session
Conclusion:
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, indoor layout with cluster-based topology is up to companies. Further discussion on the evaluations assumptions for cluster-based topology is not expected.
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, for outdoor layout, do not support UE-to-UE 2D distance smaller than 10m.
R1-2212583 FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Nov 17th session
Agreement
In evaluation methodology for commercial deployment scenario for
sidelink operation on FR2, for outdoor layout, in the pathloss model for UMi –
Street Canyon in TR38.901, antenna height of base station (
) is replaced by antenna height of UE (
).
Agreement
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, optionally support performance metric of UE satisfaction as section 7.2 in TR38.838 for XR traffic evaluation.
Conclusion
When reporting the simulation results for sidelink operation on FR2, companies should report the used beamwidth.
Conclusion
In evaluation methodology for commercial deployment scenario for sidelink operation on FR2, the UE antenna array configurations other than the one defined in Table 6.1.4-7 of TR37.885 are not precluded.
Final summary in R1-2212954.
Placeholder only. No contributions in RAN1#111.
Please refer to RP-222806 for detailed scope of the WI.
R1-2302064 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
[112-R18-SL] – Kevin (OPPO)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
Focus on FR1 unlicensed bands (n46 and n96/n102).
Including evaluation methodology for unlicensed channel access (if any).
From AI 5
Rel-18 Sidelink (continuation of discussions on RAN2 LS in R1-2210805 – LS on SL LBT failure indication and consistent SL LBT failure)
Relevant company tdocs:
R1-2300296 Discussion on SL LBT failure indication and consistent SL LBT failure OPPO
R1-2300353 Draft reply LS on SL LBT failure indication and consistent SL LBT failure ZTE, Sanechips
R1-2300406 Draft reply LS on SL LBT failure indication and consistent SL LBT failure vivo
R1-2300407 Discussion on SL LBT failure indication and consistent SL LBT failure vivo
R1-2300508 Discussion of RAN2 LS on SL LBT failure indication and consistent SL LBT failure Nokia, Nokia Shanghai Bell
R1-2300509 [Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure Nokia, Nokia Shanghai Bell
R1-2300612 Discussion on LS on SL LBT failure indication and consistent SL LBT failure CATT, GOHIGH
R1-2301122 [Draft] Reply LS on SL LBT failure indication and consistent SL LBT failure Ericsson
R1-2301123 Discussion on SL LBT failure indication and consistent SL LBT failure Ericsson
R1-2301326 Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT Apple
R1-2301327 Draft reply LS to RAN2 on SL LBT failure indication and consistent SL LBT Apple
R1-2301530 Discussion on LS on SL LBT failure indication and consistent SL LBT failure LG Electronics
R1-2301565 Discussion on LS on SL LBT failure indication and consistent SL LBT failure Sharp
R1-2301709 Discussion on RAN2 LS on SL LBT failure indication and consistent SL LBT failure Huawei, HiSilicon
R1-2301980 Moderator summary of discussion for LS reply on SL LBT failure indication and consistent SL LBT failure Moderator (vivo)
From Wednesday session
Conclusion
When a SL LBT failure is notified by PHY, RAN1 considers that indicating the granularity of SL LBT failure indication at BWP level, RB set level, or SL resource pool level, are all feasible. RAN1 leaves it to RAN2 to determine the granularity of SL LBT failure indication.
Comeback for draft LS reply.
R1-2301981 Draft reply LS on SL LBT failure indication and consistent SL LBT failure Moderator (vivo)
R1-2302117 Draft reply LS on SL LBT failure indication and consistent SL LBT failure Moderator (vivo)
Decision: The draft LS in R1-2302117 is endorsed (after correcting typo in April meeting date). Final LS is approved in R1-2302118.
R1-2300036 On Channel Access Mechanism for SL-U Nokia, Nokia Shanghai Bell
R1-2300060 Channel access mechanism for sidelink on unlicensed spectrum FUTUREWEI
R1-2300124 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2300219 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2300297 On channel access mechanism and resource allocation for SL-U OPPO
R1-2300313 Discussion on Channel Access Mechanisms Johns Hopkins University APL
R1-2300354 Discussion on channel access mechanism for SL-U ZTE, Sanechips
R1-2300386 Sidelink channel access mechanisms National Spectrum Consortium
R1-2300453 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2300576 Discussion on channel access mechanism for sidelink-unlicensed xiaomi
R1-2300680 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2300732 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2300751 Discussion on channel access mechanism for SL-U Fujitsu
R1-2300771 Clarifications on SL-U channel access mechanism CableLabs
R1-2300816 Channel Access of Sidelink on Unlicensed Spectrum NEC
R1-2300875 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2300948 On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2301002 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2301037 Considerations on channel access mechanism of SL-U CAICT
R1-2301045 Discussion on channel access mechanism for sidelink on unlicensed spectrum ETRI
R1-2301130 Channel access mechanism for SL-U Ericsson
R1-2301173 Sidelink channel access on unlicensed spectrum InterDigital, Inc.
R1-2301189 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2301264 On channel access mehanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2301297 Sidelink channel access on unlicensed spectrum Panasonic
R1-2301306 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2301346 Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum Apple
R1-2301413 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2301493 Discussion on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2301532 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
R1-2301543 Discussion on channel access mechanism for NR sidelink evolution Sharp
R1-2301584 Discussion on channel access mechanism MediaTek Inc.
R1-2301627 Channel Access Mechanism for SL-U ITL
R1-2301734 Discussion on channel access mechanism for SL-U WILUS Inc.
R1-2301790 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Monday session
Agreement
The CAPC level that should be used for S-SSB transmissions:
Agreement
The CAPC level that should be used for PSFCH transmission, CAPC value (p) should be set to 1 when UE performs Type 1 channel access procedure for PSFCH transmission.
Agreement
The end timing for the definition of reference duration in the contention window adjustment procedure for SL-U is defined as follows:
R1-2301791 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2301792 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2301793 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Wednesday session
Agreement
A CPE can be transmitted from a CPE starting position before SL transmission for the following two options:
· Option 1: within the symbol just before the next AGC symbol
· Option 2:
o within the symbol just before the next AGC symbol for 15 kHz SCS
o within at most 2 symbols just before the next AGC symbol for 30 or 60 kHz SCS
· FFS applicable scenario(s), condition(s) and channel type(s) to apply Option 1 or Option 2
Agreement
· A responding UE over a shared COT can be:
o a receiving UE, which is the target of a PSCCH/PSSCH transmission of a COT initiator
§ In the case of unicast from the COT initiator, within the same COT when the source and destination IDs contained in the COT initiator’s SCI match to the corresponding destination and source IDs relating to the same unicast at the receiving UE
§ In the case of groupcast and broadcast, when the destination ID contained in the COT initiator’s SCI match to a destination ID known at the receiving UE
o a UE identified by ID(s), if additional IDs are supported in the COT sharing information (in addition to the source and destination IDs of the PSCCH/PSSCH transmission), when additional IDs are included in the COT sharing information from the COT initiator
§ FFS Limitations on what additional IDs may be included and how they may be indicated
R1-2301794 FL summary #5 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2301795 FL summary #6 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2301796 FL summary #7 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From Friday session
Agreement
A responding UE’s SL transmission(s) within RB set(s) corresponding to a shared COT can be transmitted when the CAPC value(s) of the SL transmission(s) have an equal or smaller CAPC value than the CAPC value indicated in the COT sharing information.
Agreement
A responding UE’s PSSCH/PSCCH transmission(s) within RB set(s) corresponding to a shared COT is intended for the COT initiating UE when,
Final summary in R1-2301797.
R1-2300037 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2300061 Physical channel design for sidelink on unlicensed spectrum FUTUREWEI
R1-2300125 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2300220 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2300298 On PHY channel designs and procedures for SL-U OPPO
R1-2300355 Discussion on physical layer structures and procedures for SL-U ZTE, Sanechips
R1-2300387 Sidelink Physical Channel Design Considerations National Spectrum Consortium
R1-2300454 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2300577 Discussion on physical channel design for sidelink-unlicensed xiaomi
R1-2300681 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2300733 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2300826 Discussion on physical channel design framework NEC
R1-2300876 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2300901 Discussion on Physical channel design framework for sidelink on unlicensed spectrum Hyundai Motor Company
R1-2300949 On the Physical Layer Enhancements for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2301003 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2301839 PHY channel design framework for SL-U Ericsson (rev of R1-2301131)
R1-2301174 SL U physical layer design framework InterDigital, Inc.
R1-2301190 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2301265 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
R1-2301298 Physical channel design for sidelink on unlicensed spectrum Panasonic
R1-2301307 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2301347 Discussion on Sidelink Physical Channel Design Framework for Unlicensed Spectrum Apple
R1-2301414 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2301459 Discussion on channel structure for SL-U ASUSTeK
R1-2301494 Discussion on channel design framework in SL-U NTT DOCOMO, INC.
R1-2301533 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2301544 Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2301585 Discussion on physical channel design framework MediaTek Inc.
R1-2301628 Physical Channel Design framework for SL-U ITL
R1-2301735 Discussion on PHY channel design framework for SL-U WILUS Inc.
R1-2301928 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Monday session
Agreement
For slots with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U:
Agreement
Regarding PSFCH transmission with 15 kHz and 30 kHz SCS, RAN1 down-select one of followings, or support the combination of followings:
R1-2301929 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Wednesday session
Agreement
To address PSFCH transmission dropping due to LBT failure:
Agreement
For contiguous RB-based PSCCH/PSSCH transmission in SL-U:
Agreement
For S-SSB transmission within 1 RB set, down-select to one or more of the following for 15 kHz and 30 kHz SCS:
R1-2301930 FL summary#3 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From Friday session
Working assumption
If a resource pool includes slots with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
Agreement
Down-select one or support both of the followings:
Agreement
RAN1 further study the followings:
Agreement
RAN1 further study the followings:
Final summary in R1-2301931.
Consider additional RAN guidance on co-channel coexistence in RP-222674.
R1-2300038 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
R1-2300062 Dynamic coexistence between NR and LTE sidelink FUTUREWEI
R1-2300126 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2300221 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2300299 Discussion on dynamic resource sharing in co-channel coexistence of LTE and NR SL OPPO
R1-2300356 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ZTE, Sanechips
R1-2300380 Dynamic co-channel coexistence for LTE sidelink and NR sidelink TOYOTA Info Technology Center
R1-2300455 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2300578 Discussion on co-channel coexistence for LTE and NR sidelink xiaomi
R1-2300682 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2300734 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2300817 Co-existence between LTE and NR sidelink NEC
R1-2300877 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sony
R1-2300897 Discussion on Sidelink Co-channel Coexistence Panasonic
R1-2300950 On the Co-channel Coexistence between LTE and NR Sidelink Intel Corporation
R1-2301004 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2301046 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2301129 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2301150 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
R1-2301175 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2301191 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2301266 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2301304 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ASUSTeK
R1-2301308 Discussion of co-channel coexistence for LTE sidelink and NR sidelink Transsion Holdings
R1-2301348 Discussion on Co-channel Coexistence for LTE Sidelink and NR Sidelink Apple
R1-2301415 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated
R1-2301495 Discussion on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2301534 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2301545 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2301736 Discussion on co-channel coexistence for LTE sidelink and NR sidelink WILUS Inc.
R1-2301853 Feature lead summary #1 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
From Tuesday session
Agreement
In NR SL resource (re)selection procedure, option 1 is adopted for how to determine candidate resource set for NR SL considering the LTE SL reserved resources by other LTE SL UE
R1-2301854 Feature lead summary #2 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
From Thursday session
Working assumption
R1-2301855 Feature lead summary #3 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
From Friday session
Agreement
In NR SL resource (re)selection procedure, down-select one of followings for how to determine candidate resource set for NR SL considering the LTE SL resources selected to be used for LTE SL module’s own LTE SL transmission
Work on this sub-agenda item is to continue as a ‘study’ only objective.
R1-2300039 On Beam Management for Sidelink in FR2 Nokia, Nokia Shanghai Bell
R1-2300127 Enhanced sidelink operation on FR2 licensed spectrum Huawei, HiSilicon
R1-2300300 Sidelink beam management on FR2 licensed spectrum OPPO
R1-2300314 Discussion on Enhanced Sidelink Operation on FR2 Licensed Spectrum Johns Hopkins University APL
R1-2300357 Discussion on enhanced sidelink operation on FR2 licensed spectrum ZTE, Sanechips
R1-2300381 Discussion on enhanced sidelink operation on FR2 licensed spectrum TOYOTA Info Technology Center
R1-2300456 Enhanced sidelink operation on FR2 licensed spectrum vivo
R1-2300579 Discussion on SL beam management in FR2 licensed spectrum xiaomi
R1-2300683 Discussion on enhanced sidelink operation on FR2 licensed spectrum CATT
R1-2300735 Discussion on enhanced sidelink operation on FR2 licensed spectrum Lenovo
R1-2300827 Discussion on sidelink operation on FR2 licensed spectrum NEC
R1-2300878 Discussion on sidelink beam management on FR2 licensed spectrum Sony
R1-2300951 On Sidelink Operation in FR2 Licensed Spectrum Intel Corporation
R1-2301005 Discussion on sidelink enhancements on FR2 licensed spectrum CMCC
R1-2301132 Study aspects for sidelink in FR2 Ericsson
R1-2301176 On enhanced SL FR2 operation InterDigital, Inc.
R1-2301192 NR Sidelink Operation in FR2 Fraunhofer HHI, Fraunhofer IIS
R1-2301267 On enhanced SL Operation in FR2 Samsung
R1-2301349 Discussion on Sidelink Operation on FR2 Apple
R1-2301416 Enhanced sidelink operation on FR2 licensed spectrum Qualcomm Incorporated
R1-2301496 Discussion on enhanced sidelink operation on FR2 licensed spectrum NTT DOCOMO, INC.
R1-2301535 Discussion on enhanced sidelink operation on FR2 licensed spectrum LG Electronics
R1-2301546 Discussion on enhanced sidelink operation on FR2 licensed spectrum Sharp
R1-2301616 Discussion on SL operation on FR2 MediaTek Inc.
R1-2301694 Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation CEWiT
R1-2301737 Discussion on enhanced sidelink operation on FR2 licensed spectrum WILUS Inc.
R1-2301843 FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Tuesday session
Agreement
For sidelink beam management, RAN1 is to study
R1-2301844 FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From Thursday session
Agreement
RAN1 is to study sidelink beam measurement and reporting schemes (e.g., periodicity, contents, container, timing, procedure, etc.) for sidelink beam maintenance.
Agreement
RAN1 is to study sidelink beam indication and switching schemes (e.g., framework, general procedure, contents, signaling, timing, etc.) for sidelink beam maintenance.
Agreement
RAN1 is to study the information related to a sidelink beam failure instance that the PHY layer provides to the MAC layer.
Final summary in R1-2301845.
Placeholder only. No contributions in RAN1#112.
Please refer to RP-230077 for detailed scope of the WI.
R1-2304169 Session notes for 9.4 (NR sidelink evolution) Ad-Hoc Chair (Huawei)
From AI 5
R1-2302280 LS on Comparison of SL-RSRP and SD-RSRP measurements RAN2, Nokia
[112bis-e-R18-SL-05] – Torsten (Nokia)
Email discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements in R1-2302280 by April 26th
R1-2304074 Summary#1 - [112bis-e-R18-SL-05] Email discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements in R1-2302280 Moderator (Nokia)
Presented in April 20th GTW session
R1-2304075 Summary#2 - [112bis-e-R18-SL-05] Email discussion on RAN2 LS on comparison of SL-RSRP and SD-RSRP measurements in R1-2302280 Moderator (Nokia)
From April 24th GTW session
Agreement
RAN1 informs RAN2 that comparison of SL-RSRP and SD-RSRP measurement is affected by at least the following issues
Agreement
RAN1 replies to RAN2 that:
Comeback for draft LS to RAN2 – Torsten (Nokia)
R1-2304210 Draft Reply LS on comparison of SL-RSRP and SD-RSRP measurements Moderator (Nokia)
Decision: As per GTW decision on April 26th, the draft reply LS on comparison of SL-RSRP and SD-RSRP measurements is endorsed. Final LS is approved in R1-2304211.
Focus on FR1 unlicensed bands (n46 and n96/n102).
Including evaluation methodology for unlicensed channel access (if any).
R1-2302289 On Channel Access Mechanism for SL-U Nokia, Nokia Shanghai Bell
R1-2302324 Discussion on channel access mechanism for sidelink on unlicensed spectrum FUTUREWEI
R1-2302353 Channel access mechanism and resource allocation for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2302486 Channel access mechanism for sidelink on unlicensed spectrum vivo
R1-2302519 Sidelink channel access mechanisms National Spectrum Consortium
R1-2302549 On channel access mechanism and resource allocation for SL-U OPPO
R1-2302601 Discussion on channel access mechanism for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2302704 Discussion on channel access mechanism for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2302797 On the Channel Access Mechanisms for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2302847 Discussion on channel access mechanism for SL-unlicensed Sony
R1-2302911 Discussion on channel access mechanism for SL-U Fujitsu
R1-2302922 Discussion on channel access mechanism for sidelink on unlicensed spectrum LG Electronics
R1-2302951 Sidelink channel access on unlicensed spectrum InterDigital, Inc.
R1-2302984 Discussion on channel access mechanism for sidelink-unlicensed xiaomi
R1-2303002 SL-U Channel Access Mechanism Clarifications CableLabs
R1-2303129 On channel access mehanism for sidelink on FR1 unlicensed spectrum Samsung
R1-2303168 Sidelink channel access on unlicensed spectrum Panasonic
R1-2303189 Considerations on channel access mechanism of SL-U CAICT
R1-2303198 Discussion on channel access mechanism for sidelink on unlicensed spectrum ETRI
R1-2303235 Discussion on channel access mechanism for sidelink on unlicensed spectrum CMCC
R1-2303313 Channel access mechanism for sidelink on FR1 unlicensed spectrum Lenovo
R1-2303323 Channel access mechanism for SL-U Ericsson
R1-2303367 Discussion on channel access mechanism MediaTek Inc.
R1-2303374 Discussion of channel access mechanism for sidelink in unlicensed spectrum Transsion Holdings
R1-2303400 Discussion on channel access mechanism for SL-U ZTE, Sanechips
R1-2303484 Discussion on channel access mechanism for sidelink on FR1 unlicensed spectrum Apple
R1-2303535 NR Sidelink Unlicensed Channel Access Mechanisms Fraunhofer HHI, Fraunhofer IIS
R1-2303591 Channel Access Mechanism for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2303686 Channel Access of Sidelink on Unlicensed Spectrum NEC
R1-2303713 Discussion on channel access mechanism in SL-U NTT DOCOMO, INC.
R1-2303768 Discussion on channel access mechanism for NR sidelink evolution Sharp
R1-2303819 Channel Access Mechanism for SL-U ITL
R1-2303832 Discussion on channel access mechanism for SL-U WILUS Inc.
[112bis-e-R18-SL-01] – Kevin (OPPO)
Email discussion on channel access mechanism for unlicensed spectrum by April 26th
- Check points: April 21, April 26
R1-2303971 FL summary #1 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
Decision: As per email decision posted on April 20th,
Agreement
The existing NR-U EDT procedures for uplink transmissions is taken as the baseline for SL-U in Rel-18.
· FFS: details for S-SSB and PSFCH transmissions (e.g., EDT determination based on PC,MAX and/or network configured EDT, value for TA), if needed
Agreement
For the CPE agreements reached so far in this agenda, the 1 or at most 2 symbols just before the next AGC symbol for CPE transmission is/are physical symbol(s).
Agreement
The container for carrying the COT sharing information from a COT initiator UE includes at least the SCI.
R1-2303972 FL summary #2 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From April 20th GTW session
Agreement
For dynamic channel access mode with multi-channel case in SL-U, both NR-U DL Type A and Type B multi-channel access procedure are supported for multiple PSFCH transmissions on multiple channels.
From April 24th GTW session
Agreement
Channel access procedures for SL multi-channel transmission(s) include the following cases.
R1-2304145 [DRAFT] LS on PSFCH and S-SSB transmissions over non-contiguous RB sets Moderator (OPPO)
Decision: As per email decision posted on April 25th, the draft LS is endorsed. Final LS is approved in R1-2304218.
Decision: As per email decision posted on April 25th,
Agreement
The ACK/NACK HARQ-ACK feedback corresponding to the PSSCH for SL unicast in the reference duration for the latest SL channel occupancy for which ACK/NACK HARQ-ACK feedback is available is used as follows:
·
If ‘ACK’ is received, for
every priority class 
, 
; otherwise 
is increased to the next allowed value.
· Note: this is not applied to the case that reference duration includes multiple PSSCHs with ACK/NACK HARQ-ACK enabled, if that case is supported.
Decision: As per email decision posted on April 26th,
Agreement
The ACK/NACK HARQ-ACK feedback corresponding to the PSSCH for SL groupcast option 2 in the reference duration for the latest SL channel occupancy for which ACK/NACK HARQ-ACK feedback is available is used according to Option 2 when the ratio in Option 1 is not (pre-)configured; otherwise Option 1.
is reset to 
for every priority
class , otherwise increase for every priority
class to the next higher
allowed value. ; otherwise is increased.
R1-2303973 FL summary #3 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
R1-2303974 FL summary #4 for AI 9.4.1.1: SL-U channel access mechanism Moderator (OPPO)
From April 26th GTW session
Working assumption
When multiple CPE starting candidate positions are (pre-)configured for PSCCH/PSSCH transmission, for the case of initiating a COT
Agreement
For 15 kHz, 30kHz and 60kHz SCSs, a set of CPE starting candidate position(s) for PSCCH/PSSCH is (pre-)configured or pre-defined in the spec (to be down-selected) separately for transmission within COT and transmission outside COT.
Agreement
Send an LS to RAN2 according to the following content for the LS:
|
RAN1 has discussed the following approaches to implement/achieve MCSt for SL-U communication. RAN1 would like to seek RAN2’s opinion on the following questions.
Approach 1: “best effort for multiple TBs” ·
Step 1: Higher
layer triggers L1 resource selection for one TB with one set of parameters ( · Step 2: L1 report a set of candidate single-slot resource (SA) according to existing L1 resource allocation procedure - R16/17 behavior. · Step 3: Higher layer selects a set of resources either randomly (R16/17 behavior) or according to a consecutive-slots criterion (new behavior) to achieve MCSt. · Step 4: Repeat Step 1-3 for different TB if required.
Approach 2: “guarantee MCSt for single TB and best effort for multiple TBs” ·
Step 1: Higher
layer triggers L1 resource selection for one TB with one set of parameters ( · Step 2: L1 report a set of candidate multi-slot resource (SA) according to most of the existing L1 resource allocation procedure (FFS: RSRP calculation / threshold may need to change) · Step 3: Higher layer selects a candidate multi-slot resource either randomly (R16/17 behavior) or according to a consecutive-slots criterion (new behavior). · Step 4: Repeat Step 1-3 for different TB if required.
Approach 3: “guarantee MCSt for multiple TBs” ·
Step 1: Higher
layer triggers L1 resource (re-)selection one time for one or multiple TBs
with one set of parameters ( · Step 2: L1 report a set of candidate multi-slot resource (SA) according to most of the existing L1 resource allocation procedure (FFS: RSRP calculation / threshold may need to change) · Step 3: Higher layer selects transmission resource for the one or multiple TB(s) from the reported set of candidate multi-slot resource (SA).
Question 1 (for Approach 1/ Approach 2): feasibility of selecting the resource for a single TB in MAC layer (single-slot under Approach 1, multi-slot under Approach 2) with the principle of “concatenating” across separate resource selection triggers (across TBs)
Question 2 (for Approach 3): feasibility of triggering the resource selection procedures for multiple SL processes at the same time
Question 3 (Approach 2/ Approach 3): feasibility of providing a new parameter “number of slots for MCSt” to L1 when triggering resource (re-)selection for MCSt |
Final LS to RAN2 is approved in:
R1-2304257 LS on MCSt resource (re-)selection RAN1, OPPO
Agreement
At least the following information should be used as part of COT sharing information from the COT initiator UE.
o FFS additional ID(s)
o FFS: starting offset, number of slots, [remaining or total] COT duration, or a combination of them
· Frequency domain information of the shared COT
o FFS applicable RB set(s), FRIV, and any other(s)
· FFS: how each of the above is indicated.
· Note, other information is not precluded.
Agreement
To resolve the Type 1 LBT blocking issue, where one UE performing a Type 1 LBT procedure for using its own selected/reserved resource(s) is blocked by another UE’s SL transmission at least in a slot preceding to the selected/reserved resource and causing the LBT to fail, further study the following options in a future meeting.
Agreement
A higher layer parameter “absenceOfAnyOtherTechnology” is supported in Rel-18 for SL transmissions in unlicensed bands (e.g., by level of regulation).
Conclusion
For defining the locations of CPE starting positions, RAN1 concludes that the NR-U principle for switching gaps is reused in SL-U, that is:
Final summary in R1-2303975.
R1-2302290 On Physical Channel Design Framework for SL-U Nokia, Nokia Shanghai Bell
R1-2302325 Discussion on physical channel design for sidelink on unlicensed spectrum FUTUREWEI
R1-2302354 Physical channel design for sidelink operation over unlicensed spectrum Huawei, HiSilicon
R1-2302487 Physical channel design framework for sidelink on unlicensed spectrum vivo
R1-2302520 Sidelink Physical Channel Design Considerations National Spectrum Consortium
R1-2302550 On PHY channel designs and procedures for SL-U OPPO
R1-2302602 Discussion on Physical channel design for sidelink on unlicensed spectrum Spreadtrum Communications
R1-2302705 Discussion on physical channel design framework for sidelink on unlicensed spectrum CATT, GOHIGH
R1-2302798 On the Physical Layer Enhancements for SL Operating in Unlicensed Spectrum Intel Corporation
R1-2302848 Discussion on physical channel design framework for SL-unlicensed Sony
R1-2302923 Discussion on physical channel design framework for sidelink on unlicensed spectrum LG Electronics
R1-2302952 SL U physical layer design framework InterDigital, Inc.
R1-2302985 Discussion on physical channel design for sidelink-unlicensed xiaomi
R1-2303130 On physical channel design framework for sidelink on FR1 unlicensed spectrum Samsung
R1-2303169 Physical channel design for sidelink on unlicensed spectrum Panasonic
R1-2303199 Discussion on physical channel design framework for SL-U ETRI
R1-2303236 Discussion on physical channel design framework for sidelink on unlicensed spectrum CMCC
R1-2303314 Physical layer design framework for sidelink on FR1 unlicensed spectrum Lenovo
R1-2303324 PHY channel design framework for SL-U Ericsson
R1-2303368 Discussion on physical channel design framework MediaTek Inc.
R1-2303375 Discussion of physical channel design for sidelink in unlicensed spectrum Transsion Holdings
R1-2303401 Discussion on physical layer structures and procedures for SL-U ZTE, Sanechips
R1-2303485 On Sidelink Physical Channel Design Framework for Unlicensed Spectrum Apple
R1-2303539 NR Sidelink Unlicensed Physical Channel Design Fraunhofer HHI, Fraunhofer IIS
R1-2303592 Physical Channel Design for Sidelink on Unlicensed Spectrum Qualcomm Incorporated
R1-2303670 Discussion on physical channel design framework NEC
R1-2303714 Discussion on channel design framework in SL-U NTT DOCOMO, INC.
R1-2303769 Discussion on physical channel design framework for NR sidelink evolution on unlicensed spectrum Sharp
R1-2303820 Physical Channel Design framework for SL-U ITL
R1-2303833 Discussion on PHY channel design framework for SL-U WILUS Inc.
[112bis-e-R18-SL-02] – Mixiang (Huawei)
Email discussion on physical channel design framework for unlicensed spectrum by April 26th
- Check points: April 21, April 26
Decision: As per email decision posted on April 20th,
Agreement
Considering PSD limit in unlicensed spectrum regulation, RAN1 further study whether updates on power control is needed especially for PSFCH.
R1-2303918 FL summary#1 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From April 20th GTW session
Agreement
Regarding PSFCH transmission with 15 kHz and 30 kHz SCS:
Working assumption
Additional candidate S-SSB occasions are excluded from resource pool.
Decision: As per email decision posted on April 24th,
Agreement
A SL-BWP is (pre-)configured with either contiguous RB-based or interlace RB-based PSCCH/PSSCH transmission, i.e., not both.
Decision: As per email decision posted on April 26th,
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U, considering 1 sub-channel equals K interlace(s), support the followings:
Agreement
Regarding more than 1 PSFCH occasion per PSCCH/PSSCH transmission, support the followings:
R1-2303919 FL summary#2 for AI 9.4.1.2 SL-U physical channel design framework Moderator (Huawei)
From April 26th GTW session
Agreement
Regarding frequency domain resource indication for interlace RB-based PSSCH transmission, support the followings:
Agreement
For contiguous RB-based PSCCH/PSSCH transmission in SL-U, regarding sub-channel(s) which include intra-cell guardband PRBs, down-select one or more of the followings in RAN1#113:
Agreement
If a resource pool includes slots with 2 candidate starting symbols for a PSCCH/PSSCH transmission:
or sl-LengthSymbols or other usage of L_ref,
whether 
is determined in
the same way as in legacy NR SL, etc.
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U, regarding details of mapping between sub-channel and interlace:
Agreement
When the SL-BWP contains multiple RB sets, study the followings:
Agreement
For S-SSB transmission within 1 RB set, for 15 kHz and 30 kHz SCS, Alt6 is supported:
Note: the Options are as below
Note: Option A and B are applicable in region with no OCB requirement, or with OCB exemption.
Conclusion
Regarding additional candidate S-SSB occasions, in the same S-SSB period, UE can attempt to transmit on additional candidate S-SSB occasion(s) regardless of whether or not it transmitted on R16/R17 S-SSB occasion(s).
Agreement
For interlace RB-based PSCCH/PSSCH transmission in SL-U, support the following:
Agreement
Regarding Tx UE behavior, at least when it initiates a COT:
FFS: COT sharing case
Final summary in R1-2303920.
Consider additional RAN guidance on co-channel coexistence in RP-222674 and RP-230769.
R1-2302291 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Nokia, Nokia Shanghai Bell
R1-2302355 Co-channel coexistence for LTE sidelink and NR sidelink Huawei, HiSilicon
R1-2302488 Co-channel coexistence for LTE sidelink and NR sidelink vivo
R1-2302551 Remaining details on dynamic resource sharing OPPO
R1-2302581 Dynamic co-channel coexistence for LTE sidelink and NR sidelink TOYOTA Info Technology Center
R1-2302603 Discussion on Co-channel coexistence for LTE sidelink and NR sidelink Spreadtrum Communications
R1-2302706 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CATT, GOHIGH
R1-2302799 On the Co-channel Coexistence between LTE and NR Sidelink Intel Corporation
R1-2302849 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sony
R1-2302872 Discussion on Sidelink Co-channel Coexistence Panasonic
R1-2302924 Discussion on co-channel coexistence for LTE sidelink and NR sidelink LG Electronics
R1-2302953 Co-channel coexistence for LTE sidelink and NR sidelink InterDigital, Inc.
R1-2302986 Discussion on co-channel coexistence for LTE and NR Sidelink xiaomi
R1-2303131 On co-channel coexistence for LTE sidelink and NR sidelink Samsung
R1-2303200 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ETRI
R1-2303237 Discussion on co-channel coexistence for LTE sidelink and NR sidelink CMCC
R1-2303315 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Lenovo
R1-2303325 Co-channel coexistence between LTE sidelink and NR sidelink Ericsson
R1-2303376 Discussion of co-channel coexistence for LTE sidelink and NR sidelink Transsion Holdings
R1-2303402 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ZTE, Sanechips
R1-2303486 On Co-channel Coexistence for LTE Sidelink and NR Sidelink Apple
R1-2303540 Discussion on Co-Channel Coexistence for LTE and NR Sidelink Fraunhofer HHI, Fraunhofer IIS
R1-2303976 Co-channel Coexistence Between LTE SL and NR SL Qualcomm Incorporated (rev of R1-2303593)
R1-2303687 Co-existence between LTE and NR sidelink NEC
R1-2303715 Discussion on co-channel coexistence of LTE-SL and NR-SL NTT DOCOMO, INC.
R1-2303770 Discussion on co-channel coexistence for LTE sidelink and NR sidelink Sharp
R1-2303787 Discussion on co-channel coexistence for LTE sidelink and NR sidelink ASUSTeK
R1-2303791 Co-channel coexistence for LTE sidelink and NR sidelink Continental Automotive
R1-2303834 Discussion on co-channel coexistence for LTE sidelink and NR sidelink WILUS Inc.
R1-2303848 On sidelink co-channel coexistence issues Mitsubishi Electric RCE
[112bis-e-R18-SL-03] – Seungmin (LGE)
Email discussion on co-channel coexistence for LTE-NR SL by April 26
- Check points: April 21, April 26
R1-2302931 FL Summary #1 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
From April 18th GTW session
Agreement
In NR SL resource (re)selection procedure, for dynamic resource pool sharing, the list of initial SL RSRP thresholds is separately (pre)configured (i.e., Alt 3 in the agreement of RAN1#112 meeting) for the PHY layer of NR SL module to exclude NR SL candidate resources overlapping with LTE SL reserved resources by other LTE SL UE.
Agreement
In NR SL resource (re)selection procedure, for determining the LTE SL periodic reserved resources by other LTE SL UE, the formula of Q in Section 8.1.4 in TS 38.214 is used.
Note: The reservation period and the location of the LTE SL periodic reserved resources are determined based on the set of LTE SL logical subframe that may belong to LTE SL resource pool as specified in TS 36.213.
R1-2302932 FL Summary #2 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
R1-2302933 FL Summary #3 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
R1-2304110 FL Summary #4 for AI 9.4.2: Co-channel coexistence for LTE sidelink and NR sidelink Moderator (LG Electronics)
From April 24th GTW session
Agreement
In NR SL resource (re)selection procedure, the PHY layer of NR SL module excludes NR SL candidate resources overlapping with LTE SL resources associated with non-monitored subframe (in which UE has not monitored due to its transmission) in LTE SL module
Agreement
In NR SL resource (re)selection procedure for dynamic resource pool sharing, the PHY layer of NR SL module excludes NR SL candidate resources in a NR SL slot overlapping with LTE SL resources selected to be used for LTE SL module’s own LTE SL transmission
Agreement
For NR SL transmissions of 30kHz SCS with dynamic resource pool sharing, the power level of the NR PSCCH/PSSCH transmission in the first of NR SL slots overlapping with an LTE SL subframe is always larger than or equal to the power level(s) of the NR PSCCH/PSSCH transmission in the subsequent NR SL slot overlapping with the LTE SL subframe.
Decision: As per email decision posted on April 27th,
Agreement
When the same TB is transmitted on the NR SL slots overlapping with the LTE SL subframe, it is up to UE implementation how to avoid transmitting NR PSCCH/PSSCH only in the subsequent NR SL slot overlapping with an LTE SL subframe according to RAN#99’s agreement for NR PSCCH/PSSCH transmissions of 30kHz SCS with dynamic resource pool sharing
Agreement
RAN1 does not pursue further enhancements except for the following to handle NR SL candidate resources overlapping with LTE PSCCH for non-adjacent LTE SL resource pool in NR SL resource (re)selection procedure for dynamic resource pool sharing in Rel-18.
Agreement
In NR SL resource (re)selection procedure, the PHY layer of NR SL module excludes NR SL candidate resources where the corresponding PSFCH transmission occasions overlap with LTE SL reserved resources by other LTE SL UE in time domain, Down-selection one of followings:
Agreement
The NR SL module uses the information from the starting LTE SL subframe to the ending LTE SL subframe in the shared information from the LTE SL module.
Final summary in R1-2304178.
Work on this sub-agenda item is to continue as a ‘study’ only objective.
R1-2302292 On Beam Management for Sidelink in FR2 Nokia, Nokia Shanghai Bell
R1-2302356 Enhanced sidelink operation on FR2 licensed spectrum Huawei, HiSilicon
R1-2303881 Enhanced sidelink operation on FR2 licensed spectrum vivo (rev of R1-2302489)
R1-2302552 On sidelink beam management in FR2 OPPO
R1-2302582 Discussion on sidelink beam management on FR2 licensed spectrum TOYOTA Info Technology Center
R1-2302604 Discussion on enhanced sidelink operation on FR2 licensed spectrum Spreadtrum Communications
R1-2302707 Discussion on enhanced sidelink operation on FR2 licensed spectrum CATT
R1-2302800 On Sidelink Operation in FR2 Licensed Spectrum Intel Corporation
R1-2302850 Discussion on sidelink beam management on FR2 licensed spectrum Sony
R1-2302925 Discussion on enhanced sidelink operation on FR2 licensed spectrum LG Electronics
R1-2302954 On enhanced SL FR2 operation InterDigital, Inc.
R1-2302987 Discussion on SL beam management in FR2 licensed spectrum xiaomi
R1-2303132 On enhanced SL Operation in FR2 Samsung
R1-2303238 Discussion on sidelink enhancements on FR2 licensed spectrum CMCC
R1-2303305 Discussion on evaluation methodology and inital results for beam enhancement on sidelink FR2 operation CEWiT
R1-2303316 Discussion on enhanced sidelink operation on FR2 licensed spectrum Lenovo
R1-2303326 Study aspects for sidelink in FR2 licensed spectrum Ericsson
R1-2303369 Discussion on SL operation on FR2 MediaTek Inc.
R1-2303377 Discussion of sidelink operation on FR2 Transsion Holdings
R1-2303403 Discussion on enhanced sidelink operation on FR2 licensed spectrum ZTE, Sanechips
R1-2303487 On Sidelink Operation on FR2 Apple
R1-2303541 NR Sidelink Operation in FR2 Fraunhofer HHI, Fraunhofer IIS
R1-2303594 Enhanced sidelink operation on FR2 licensed spectrum Qualcomm Incorporated
R1-2303671 Discussion on sidelink operation on FR2 licensed spectrum NEC
R1-2303716 Discussion on enhanced sidelink operation on FR2 licensed spectrum NTT DOCOMO, INC.
R1-2303771 Discussion on enhanced sidelink operation on FR2 licensed spectrum Sharp
R1-2303835 Discussion on enhanced sidelink operation on FR2 licensed spectrum WILUS Inc.
[112bis-e-R18-SL-04] – Chunxuan (Apple)
Email discussion on SL operation for FR2 by April 26th
- Check points: April 21, April 26
R1-2303903 FL summary #1 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From April 18th GTW session
Agreement
· RAN1 can study the following candidate procedure where initial beam pairing is performed before sidelink unicast link establishment, including at least the following steps and how to determine UE2:
· UE1 sends reference signals via different transmit beams
o Note: multiple reference signals transmissions (e.g. repetitions) from each of the beams can be studied
o FFS when reference signals are sent
o FFS applicable reference signal
· UE2 measures the reference signals and determines a UE1 transmit beam and/or a UE2 receive beam
o FFS:whether/how to determine a UE2 transmit beam
· UE2 indicates to UE1 the determined UE1 transmit beam
o FFS how to indicate the determined transmit beam, including its feasibility
· UE1 and UE2 set up sidelink unicast link using the determined beam, following existing link establishment procedure.
Decision: As per email decision posted on April 23rd,
Agreement
Consider one or more of the following items as sidelink beam reporting contents for beam maintenance:
· Beam indication (e.g., CRI)
· L1-RSRP
· FFS: L1-SINR or other reporting contents if necessary enhancement is identified.
· Note: This does not preclude performing beam maintenance without any beam reporting
Agreement
The container(s) of sidelink beam reporting for beam maintenance is at least selected from the following options:
· Option 1: SL PHY layer signal (e.g., PSFCH, SCI)
· Option 2: SL MAC CE
· FFS: PC5-RRC, Signaling over Uu link (e.g., UCI)
Conclusion
RAN1 to prioritize the case where a UE is incapable of simultaneous transmitting or receiving PSCCH/PSSCH/PSFCH using different beams in Rel-18.
Agreement
For UE1 and UE2 in a unicast link, RAN1 to study the selection of both UE1’s transmit beam and UE2’s corresponding receive beam.
· Note: this applies for both PSCCH/PSSCH transmission/reception and PSFCH transmission/reception.
Agreement
Consider using sidelink CSI-RS as a starting point for beam maintenance.
· FFS: whether/how to enhance existing aperiodic and non-standalone SL CSI-RS
· FFS: periodic and/or semi-persistent SL CSI-RS transmissions
· FFS: standalone SL CSI-RS transmissions
· FFS: one or multiple SL CSI-RS transmissions within one slot
· FFS: SL CSI-RS transmissions with or without repetition on transmit beams
R1-2303904 FL summary #2 for AI 9.4.3 Enhanced sidelink operation on FR2 licensed spectrum Moderator (Apple)
From April 24th GTW session
Agreement
RAN1 can study the following candidate procedure where initial beam pairing is performed during sidelink unicast link establishment
· UE1 sends PSCCH/PSSCH that carries unicast link establishment message (e.g., DCR message) via different transmit beams
· if UE2 successfully decodes one (or more) of the PSCCH/PSSCH(s) and UE2 determines to establish a unicast link with UE1, it indicates to UE1 one (or more) UE1 transmit beam(s) of PSCCH/PSSCH(s) which is successfully received
· UE1 uses one of the indicated beam(s) to finish the remaining sidelink unicast link establishment procedure with UE2
· FFS: use of additional reference signal or additional messages or additional measurement for efficient beam pairing.
Agreement
RAN1 can study the following candidate procedure where initial beam pairing starts after sidelink unicast link establishment between UE1 and UE2, including studying whether and in which cases initial beam pairing after sidelink unicast link establishment is feasible.
· UE1 and/or UE2 use the configured resources to transmit reference signals and determine a pair of transmit beam and receive beam based on beam sweeping.
o FFS applicable reference signal(s)
o FFS whether/how to indicate the determined beams between UE1 and UE2
· FFS difference between initial beam pairing (after sidelink unicast link establishment) and beam maintenance
Agreement
To study the feasibility of adapting S-SSB for initial beam pairing between UE1 and UE2, at least the following can be considered.
Decision: As per email decision posted on April 26th,
To study the feasibility of reusing SL CSI-RS for initial beam pairing, at least the following enhancements can be considered.
Agreement
RAN1 is to study sidelink Beam Failure Recovery (BFR) mechanism at least for the scheme where SL BFI is triggered based on the measurement of reference signal for BFD (if supported), including
Agreement
Consider the following two options for determining PSFCH transmit/receive beam for a single PSFCH transmission/reception in a slot.
Final summary in R1-2303905.
Placeholder only. No contributions in RAN1#112bis-e.
